Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Designers: "Why does this text look different in Firefox? Make it look like Chrome."


lol yes, that's definitely going to happen. However, in this case, I think it's warranted. I've had so many incidents with designers, where they don't like how a line wraps, and want it to break at a more reasonable point. If the text is static, just toss in a <br> and you're done. But with dynamic text, it's just not practical at all to try to fix, so I tell my designers that they have to live with it.

I'm excited about this feature!


Even for static text, line breaks (<br>) can cause unexpected results unless you check at varying viewports. Non-breaking spaces may provide a better option, depending on the specifics of the situation.


Yep, exactly. Though the sheer complexity of the problem makes me really curious how this is implemented under the hood. I'm surprised there aren't parameters devs can use to modify this behavior.


Leaving stuff like this to be interpreted by the User-Agent is simply a tragedy.


This is why I have "Best viewed in Netscape 800x600" button on my page.


I dunno… I kind of miss the days when every site wasn’t statically pixel perfect and text just sorta flowed around and did something sensible based on your browser window size, zoom level, etc. It allowed people to focus on the content over the presentation. But I can also understand the apprehension —- it feels like a recipe for arbitrary fragmentation.


I wonder if it is acceptable now because this is bound to be pretty dynamic across viewport sizes and resolutions. So perhaps they are allowing browsers to pick an algorithm they find best suited. Changing the algorithm afterwards will probably not break anything that wouldn’t be broken by a user shrinking their window.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: