User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_5; en-us) AppleWebKit/533.19.4 (KHTML, like Gecko) Version/5.0.3 Safari/533.19.4 Build Identifier: 4.0b7 testing firefox 4beta. I would like to use the feedback button but everytime I use it, it says I need the latest firefox. I redownloaded beta twice and still the button tells me I need the latest. so how can I send feedback during this beta test? Reproducible: Always Steps to Reproduce: 1.click on feedback button 2.click on I am happy or sad about firefox 3. Actual Results: keeps going to the page stating I need the latest firefox which I already have Expected Results: want to send feedback on firesfox but feedback button not working atleast not yet
Surely this can't be too hard to fix. Either the logic in the test comparison between the user's installed version and Mozilla's latest beta version is returning FALSE when it should be TRUE or the comparison string on the Version host is not the same as that on the users installation.
Mozilla is nearing the beta 8 release. As I understand bug 582257 is the best they can do at this time. Currently http://svn.mozilla.org/libs/product-details/firefoxDetails.class.php says that beta 8 is the current build and rejects feedback from older builds.
Component: General → Input
Product: Firefox → Webtools
QA Contact: general → input
Version: unspecified → 2.0
CCing Legneato: Is Beta 8 already released? If not, we shouldn't update the product details yet: It breaks Firefox Input.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Aparently, it must be released yesterday (second http://svn.mozilla.org/libs/product-details/history/firefoxHistory.class.php).
It's because mozilla.com does not auto-update its library data while Input does.
Beta 8 is not officially live yet. Patience. I'll take this as it should be fixed when I push p-d
Assignee: nobody → clegnitto
Input shouldn't auto-update...it should always use the revision that mozilla.com checks out into /includes....
(In reply to comment #13) > Input shouldn't auto-update...it should always use the revision that > mozilla.com checks out into /includes.... Input is auto-updating quite intentionally, so that IT does not manually need to push changes when a new version is released. I'll ponder how we can improve this in the future.
Can you use the json feeds from mozilla.com? The data is there (http://www.mozilla.com/includes/product-details/json/firefox_versions.json and http://www.mozilla.com/includes/product-details/json/mobile_details.json) and will ensure you are always in sync with the homepage.
(FWIW I plan on bring up a system that is a single source of truth for this sort of thing next quarter or so).
(In reply to comment #16) > (FWIW I plan on bring up a system that is a single source of truth for this > sort of thing next quarter or so). We should discuss this. There are a handful-or-so of consumers using the django-mozilla-product-details (sic!) library. If we want to build a web service that's fed by releng's build scripts and spits out JSON on demand, I am game.
(In reply to comment #17) > (In reply to comment #16) > > (FWIW I plan on bring up a system that is a single source of truth for this > > sort of thing next quarter or so). > > We should discuss this. There are a handful-or-so of consumers using the > django-mozilla-product-details (sic!) library. If we want to build a web > service that's fed by releng's build scripts and spits out JSON on demand, I am > game. That's the plan. We'll take this offline. I'll be sending a meeting around about it and will be sure to include you. The planned system is actually why I started pulse...I went to build it and realized I needed events from the build system.
This should be fixed now that we are live. Closing. We can clone for potential input.mozilla.com improvements so it doesn't pull from trunk.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
I just tried to report a feedback in 4.0rc1 (by Help and Submit Feedback) and got the below: And YES cookies ARE enabled... CSRF Protection Error There was an error verifying your CSRF token. Your request could not be processed. We apologize for the inconvenience! The most likely cause of this error is that your browser is set up not to accept cookies from us. Please follow these instructions to enable cookies in Firefox, then try again. If the problem persists, please file a bug. Thanks!
This bug is now showing itself in Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:2.0b13pre) Gecko/20110309 Firefox/4.0b13pre
Jim: That's a different bug. 4.0b13pre is a nightly, support for which is not yet implemented.
Component: Input → General
Product: Webtools → Input
You need to log in before you can comment on or make changes to this bug.