News for hackers. Stuff that matters.
Re:Defensive CSS by webstrand on Wednesday July 06, 2022 @06:31PM (#32007719)
But what about user-agents that override font-face and font-size? Those are important accessibility features for people with poor vision or dyslexia.

Without knowing the rendered width of the text string, you can't limit the text ahead of time. Or are you saying that all designs that can't accommodate text-wrapping should be avoided?

Re:Defensive CSS by danielheath on Wednesday July 06, 2022 @07:15PM (#32008071)
If the user has large text because they can’t read easily, how is clipping it short going to help them read it?
Re:Defensive CSS by webstrand on Wednesday July 06, 2022 @07:28PM (#32008165)
Usually when the layout breaks, functionality is lost: buttons can't be clicked on, text can't be read, content is obscured to the right, etc. If none of these things are happening, I'd agree not clipping is fine.
Re:Defensive CSS by account42 on Thursday July 07, 2022 @05:10AM (#32011606)
Do you have any data to back up that "usually"? IME more often than not the only reason why content is clipped is because of looks not because of functionality. This also applies to the example in the article.

The HTML default is to flow elements to make space for larger conent. You need to go out of your way to break that.

Re:Defensive CSS by totetsu on Thursday July 07, 2022 @12:56AM (#32010075)
Or using a page translation service.