[Bug 15555] Figure out which feature strings should be supported

https://www.w3.org/Bugs/Public/show_bug.cgi?id=15555

--- Comment #6 from Aryeh Gregor <ayg@aryeh.name> ---
(In reply to comment #5)
> Actually, we want to remove everything we can get away with, including
> features that might be in use (e.g. the attribute stuff). That's the way the
> DOM standard has been written.
> 
> The cost of keeping something forever is greater than some short term hassle.

Not if the definition and implementation take about five lines each.  Then the
cost of keeping it forever is approximately zero, in the scope of the web
platform's complexity.  Saying we should break pages for the sake of
hypothetical gains in long-term platform simplicity sounds like a smaller-scale
version of the XHTML 2.0 argument.  Browsers cannot afford to make more than
very few short-term sacrifices, because they'll lose market share, and we need
to save those sacrifices for where they're really worth it.  I think the
approach to useless functions/attributes that are implemented by all browsers
should be to make them no-ops, not remove them.

I asked on the Gecko bug what people think.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.