Notable moments in Firefox for Android UA string history
Back by popular demand*, here’s a follow-up to my blog post on Firefox Desktop UA string changes. (*actual demand for this blog post asymptotically approaches zero the further you read) Early versions of Firefox for Android used a Linux desktop UA string with a Fennec/<fennecversion> product token appended to the end. Since version 41, Firefox for Android has (generally) followed the following UA
Notable moments in Firefox desktop pre-release UA string history
Notable moments in Firefox desktop pre-release UA string history I’m sure everyone remembers this super great blog post from 2010 about changes in the Firefox 4 user agent string. In terms of “blog posts about UA string changes”, it’s, well, one of them. The final post-v4 release desktop UA string is as follows: Mozilla/5.0 (<platform>; rv:<geckoversion>) Gecko/20100101 Firefox/<firefoxversion> As
Google Tier 1 Search in Firefox for Android Nightly
Late last week we quietly landed a Nightly-only addon that spoofs the Chrome Mobile user agent string for Google Search (well, Facebook too, but that’s another blog post). Why? Bug 975444 is one of the most-duped web compat bugs, which documents the fact that the version of Google Search that Firefox for Android users receive is a less rich version than the one served to Chrome Mobile. And people
hyperlinks in buttons are probably not a great idea
Over in web-bug #9726, there’s an interesting issue reported against glitch.com (which is already fixed because those peeps are classy): Basically, they had an HTML <button> that when clicked would display:block a descendent <dialog> element that contained some hyperlinks to help you create a new project. The simplest test case: Problem is, clicking on an anchor with an href inside of a button doe
How not to feature detect
Bug 1331638 is a good example of why feature detection is important, but also a good reminder to test in enviroments where the feature totally doesn’t exist. A website (Twitter, in this example) tries to do the right thing and check for support before throwing notifications at you: this.isSupported = function() { var a = "PushManager" in window, b = this.getNotificationPermission() !== "denied", c
Report Site Issue button in Firefox Nightly
In Bug 1324062 we’re landing a new button to the default hamburger menu panel in Firefox Nightly, like we did in Firefox for Android Nightly and Aurora. For now, the plan is for this feature to be Nightly-only, maybe one day graduating up to Beta. If you click it, Firefox will take a screenshot of the page you’re on and open the new issue form on webcompat.com (you can remove the screenshot before
MITM compatibility issues
(Alternate title: Kaspersky is one typo away from being called Kaspesky) Bug 1271875 is an interesting case of a compat issue not caused by a website, or a browser, but by a 3rd party. In this case, Kaspersky AntiVirus. Apparently they Malcolm in the Middle you to keep you safe: I guess that’s normal for Anti-Virus programs? (Personally I stay safe via a combination of essential oils and hyper-lin
Upcoming changes to the Firefox for Android UA string
If there’s one thing that developers love more than the confusing nature of User Agent strings, it’s when they change. Great news, everybody. Beginning in Firefox for Android 41, the default UA string will contain the Android version in the platform token (bug here): Mozilla/5.0 (Android <Android version>; Mobile; rv:<Gecko version>) Gecko/<Gecko version> Firefox/<Gecko version> And perhaps the on
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Firefox for iOS User Agent String
CircleKSunkus and CSS Zoom