Gervase Markham wrote:
> Gervase Markham wrote:
>> Changing Camino would be construed as giving up on that line. So it 
>> was requested in the bug that a discussion be started.
> 
> My view: up to now, UAs have been in continuous retreat, with greater 
> lengthenings. First there was Mozilla/X.X - but then too many people 
> sniffed that, and so it got stuck. And so on.
> 
> At last, we've finally figured out that what people should be looking 
> for is rendering engines, not browser versions. WebKit has WebKit/foo, 
> Gecko has Gecko/bar, and so on. This has the potential to stop this 
> ridiculous ever-lengthening UA string problem.
> 
> It would be a great shame to give up on that for the sake of a small 
> handful of sites. And it is a small handful - the bug in question had 29 
> dependencies last time I looked, and not all of them are relevant to 
> Camino.
> 
> On the other hand, as I said in another message, we need to do better 
> than just tell the Camino team to suck it up. And I hope we can come up 
> with a plan for that.

I think the idea of removing Firefox from the version string is a
possible solution to this. We could do that for Firefox 3, starting
with the next alpha. As a major release, and a major rev in Gecko,
it will get plenty of attention. We can have some people write web
developer articles on our UA sniffing policy and why we have it
("keeping the web open" and "preserving choice and innovation"!) and
how to check for Gecko in the UA string, and publish those over the
summer, to make sure more web developers sit up and pay attention.
I'm volunteering right now to provide editorial review to anyone who
does that. :)

If we find that the Web really can't take it, we can put Firefox
back in the UA string with the first post-3.0 security release and
let Camino do the same.

Meanwhile, let's see if this can get webmasters to fix their sniffing
code. This is totally in line with our overall mission as an organization;
I think we should try it.

~fantasai
_______________________________________________
dev-tech-layout mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-layout

Reply via email to