Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 2
    I have to disagree. For me that's an awesome feature, but also for me it's logical that the design gets broken if I resize something with external means. ... Great, that now means I have to look up on how to make the browser completely ignore that setting? Commented Jan 12, 2012 at 7:50
  • @Bobby It's not really an "external means"; it's part of the CSS standard. If this was e.g. some browser addon that does this, we could ignore it; it would be just like changing CSS via Firebug, which is obviously not supported by us. But the resizing is part of the standard, and Firefox and Chrome chose the wrong default value. So just like other issues where browsers are broken, we have to make sure that we're somewhat cross-browser compatible. Commented Jan 12, 2012 at 7:56
  • Oh, I didn't know it was in the CSS3 standard that way. I never saw it as part of the page itself, so I never expected it to work with the side, and if stuff got broken I just accepted that. That it is in the standard changes that, of course. Though I'd like to tell you that it is nonsense to disable it completely (because it sucks for me, I was using that extensively and didn't care for the broken layout), I can completely understand that point. Commented Jan 12, 2012 at 8:10
  • 1
    Agreed, for the most part. We probably wouldn't have touched it if there had been no complaints. Anyway, as I said in that answer, we have no problem with specifically enabling it in spots where it makes sense and doesn't cause issues. We just default to off, like the W3C intended. Commented Jan 12, 2012 at 8:26