You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See http://code.google.com/p/ua-parser/
Your “Browserscope thinks you are using SeaMonkey 2.2.2 No?” link points
to ua-parser’s googlecode issue tracker instead of github. This suggests that
you are not actually actively updating browserscope with the latest versions of
ua-parser from github and instead are still grabbing the outdated googlecode
copy.
Original issue reported on code.google.com by ohnobinki on 7 Nov 2013 at 4:22
The text was updated successfully, but these errors were encountered:
And your “browserscope thinks you’re using <browser> <version> No?” STILL
links to ua-parser at googlecode. Do you guys at browserscope even exist? I bet
that none of the fixes for bugs reported to ua-parser by your users are even
being pulled deployed to browserscope because you don’t know that ua-parser
is alive…
You should really take responsibility for your users and have the “No?”
link point to your own issues site. Handle pushing the bugs upstream to
ua-parser yourselves. It is irresponsible to say “this is ua-parser’s
fault” when it’s *your deployment of ua-parser*. Even more so when your
ua-parser is way out of date or if you use a patched version of ua-parser.
Original comment by ohnobinki on 12 Feb 2014 at 4:16
FYI - the regexes.yaml file was updated within the last 3 weeks and
periodically we have looked at issues filed from Browserscope to ua-parser. I'm
going to remove the "No?" link for now.
Original comment by els...@gmail.com on 12 Feb 2014 at 4:28
Original issue reported on code.google.com by
ohnobinki
on 7 Nov 2013 at 4:22The text was updated successfully, but these errors were encountered: