92.50 KB, image/png
It appears that the new AAQ form doesn't properly detect installed plugins and version of Firefox and OS. See screenshot.
And your user-agent is? Are you using Namaroko?
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.3a1pre) Gecko/20090929 Minefield/3.7a1pre It should be able to detect my OS and plugins regardless, no?
(In reply to comment #3) > Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.3a1pre) Gecko/20090929 > Minefield/3.7a1pre > > It should be able to detect my OS and plugins regardless, no? It does, and prints it out in the actual forums posts, just not in the AAQ form; I was confused by this as well, and filed bug 517310. See the decision made the James and Cheng in https://bugzilla.mozilla.org/show_bug.cgi?id=517310#c2.
That decision confuses me. Why aren't we filling the info we can extract from the UA and plugins? Regardless of version of Firefox/Minefield/etc, we should be able to detect running plugins.
We looked at data from Omniture and less than 1% of all hits are even potentially using pre-release builds (Omniture doesn't identify them very reliably, either). (I'd be interested to know how many threads are started by users running pre-release versions, maybe Cheng can help with that metric. My hypothesis is that it's far less than 1%.) Based on that, we decided that keeping the detection up to date with all possible UAs wasn't worth it. Either way, we can refactor to avoid the isFirefox() check or decide to keep update the detection for all major UAs, but I think it's a very low priority based on the Omniture data.
Summary: AAQ form doesn't detect OS/Fx version details → AAQ form doesn't detect OS/Fx version details for Beta
Summary: AAQ form doesn't detect OS/Fx version details for Beta → AAQ form doesn't detect OS/Fx version details for users of nightly builds
Target Milestone: 1.4.1 → 1.4.2
Did we have plugins+UA detection for nightly builds before, or have we never had it? If we had it before, I'd be interested to hear why we had to remove it. It we've never had it, I'm fine with keeping it that way (and WONTFIX this bug).
We always get the UA string in the resulting post -- we just don't auto-guess in the form for people not running Firefox. After getting this clarified in today's sumodev meeting, I am wontfixing this. Thanks all and sorry for the waste of time here!
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WONTFIX
Assigning to James for historical reasons :)
Assignee: nobody → james
You need to log in before you can comment on or make changes to this bug.