[whatwg] Target Attribute Values
mk98762 at gmail.com
Sat Apr 28 05:23:25 PDT 2007
Smylers <Smylers at stripey.com> wrote:
>But _requiring_ user agents to offer opt-outs seems excessive, and
>possibly beyond the jurisdiction of the spec.
Possibly, but then what's the point of making _blank non conforming if
it is not trying to be a benefit to users by discouraging its use. It
has nothing to do with client interoperability, real world web browsers
will continue to support _blank regardless.
>if somebody wanted to produce a web browser that, say, was
>so minimalist it didn't offer any user preferences at all, surely that's
>up to the browser manufacturer?
Possibly, the HTML4 spec mentions a browser UI facility to select
between alternate stylesheets as a should. The CSS2.1 draft lists it as
a must in the UA conformance section, it is also a CSS conformance
requirement to offer a UA UI facility to turn off stylesheets.
Browser manufacturers can ignore such, the only effect is that they
can't claim to be spec conforming.
User demand for such UI features expressed to the manufacturer is one
way to get such features implemented. Other web specs have seen fit to
add their weight to get UI features implemented.
More information about the whatwg