canmove, Confirmed users
1,126
edits
(→Notes: Adding suggestion of hard-coding specific sites, mentioned on the newsgroups (feel free to make less verbose)) |
m (→Notes: Typo fix) |
||
Line 41: | Line 41: | ||
* One alternative to UA string changes is evangelism. Particularly if only a few widely-used libraries need to be changed, it may be possible to bend the web to our will. Mozilla has done this before around the time of the Netscape 6 and Mozilla 1.0 releases with a massive evangelism effort. We can do that again if we have a task to rally around. | * One alternative to UA string changes is evangelism. Particularly if only a few widely-used libraries need to be changed, it may be possible to bend the web to our will. Mozilla has done this before around the time of the Netscape 6 and Mozilla 1.0 releases with a massive evangelism effort. We can do that again if we have a task to rally around. | ||
* Another alternative (that some competing browsers use) is to send a modified UA to specific popular sites in order to ensure that they receive the most appropriate content, regardless of broken UA assumptions on those | * Another alternative (that some competing browsers use) is to send a modified UA to specific popular sites in order to ensure that they receive the most appropriate content, regardless of broken UA assumptions on those sites. Whilst hard-coding specific sites is suboptimal, it may still be preferable to giving all other sites a more detailed UA, which will only encourage further problems later on. This need only be a temporary measure until the evangelism efforts above pay off - and could be implemented via about:config, or else a "ship-by-default on platform/form-factor X" addon that can easily be disabled by the user. | ||
* For the best chance of success, proposals for change should to be accompanied by documented evidence of the improvements they bring. | * For the best chance of success, proposals for change should to be accompanied by documented evidence of the improvements they bring. |