2 ms·

It's interesting -- when I have my software company that builds web apps hat on, I assume that if there's a rendering problem with a new browser, it's our probl

It's interesting -- when I have my software company that builds web apps hat on, I assume that if there's a rendering problem with a new browser, it's our problem: these guys lead the standards groups, so we fix our app as best we can, and remember that people are used to seeing occasionally broken stuff on the internet. Not the end of the world. That's contrary to this point of view, and maybe just speaks to how IT and internal corporate application mindsets are different.

Silhouette 15y ago
> when I have my software company that builds web apps hat on, I assume that if there's a rendering problem with a new browser, it's our problem I used to assume that, but I've spent so much time in the past few months fixing silly bugs that really were regressions in mainstream browsers that my default is now to assume that if something works in two or three browsers but not another then they really have broken something. This is why I have been so critical of the rapid updates policy in various recent discussions.
- vessenes 15y ago
  Interesting.. And frustrating! I haven't had that experience so far; got any tips on what to avoid right now?
  - Silhouette 15y ago
    For no browser in particular, or in some cases for several of them: - Typography (text rendering that is actually illegible on some platforms, due to basic kerning issues, poor antialiasing when CSS3 effects are applied, misapplication of OpenType features, and so on) - Java applets (outright crashing, or more annoying things like not quite passing keyboard/mouse events through properly) - HTML5 video (which encoding shall we use this week?) - CSS3 rounded corners and gradients (assorted rendering bugs that made these look awful if you'd relied on the new features) All of these have been pushed in minor/point releases, with the exception of Google dropping H.264 video support, where they appear to have quietly done a U-turn at some point having made a big announcement that they were going to push it.

Silhouette 15y ago

> when I have my software company that builds web apps hat on, I assume that if there's a rendering problem with a new browser, it's our problem I used to assume that, but I've spent so much time in the past few months fixing silly bugs that really were regressions in mainstream browsers that my default is now to assume that if something works in two or three browsers but not another then they really have broken something. This is why I have been so critical of the rapid updates policy in various recent discussions.

vessenes 15y ago
Interesting.. And frustrating! I haven't had that experience so far; got any tips on what to avoid right now?
- Silhouette 15y ago
  For no browser in particular, or in some cases for several of them: - Typography (text rendering that is actually illegible on some platforms, due to basic kerning issues, poor antialiasing when CSS3 effects are applied, misapplication of OpenType features, and so on) - Java applets (outright crashing, or more annoying things like not quite passing keyboard/mouse events through properly) - HTML5 video (which encoding shall we use this week?) - CSS3 rounded corners and gradients (assorted rendering bugs that made these look awful if you'd relied on the new features) All of these have been pushed in minor/point releases, with the exception of Google dropping H.264 video support, where they appear to have quietly done a U-turn at some point having made a big announcement that they were going to push it.