I can reproduce this Behavior back to Firefox 2 Branch. Nonetheless, it's WFM in Chrome/Opera.
Component: General → General
Product: Firefox → Core
QA Contact: general → general
Depends on: 660549
Thanks to all for your work on this issue (and same remark for all other great work you do for the mozilla foundation! :) Just for my personal knowledge : at which time the status of a bug leave the UNCONFIRMED status in the mozilla bug processing workflow ? And who is in charge of various steps (reproduce, fix, test, validate, ... ) in the mozilla foundation ? I suppose it is related to the bugzilla bug's life cycle http://www.bugzilla.org/docs/4.0/en/html/lifecycle.html But I could not find relevant information.
Just wait for Bug 660549 to get fixed on a Nightly and see if your Issue persists. If "no" this may end as a Dupe. If "yes" this can be set to "New". Thus UNCONFIRMED is okay for now. Just don't over-interpret the Status Field's Meaning ;-).
Isn't this a dupe of 677430 ? Anyway, 660549 should go first I guess.
Reproducible: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Firefox/24.0 ID:20140923194127 CSet: 63ce8133f1cc WFM with: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0 ID:20150320202338 CSet: df45b1c67169 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:39.0) Gecko/20100101 Firefox/39.0 ID:20150330030203 CSet: 6082a98d3861 => dupe to Bug 737851 (via Bug 660549)
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
No longer depends on: 660549
Resolution: --- → DUPLICATE
Duplicate of bug: 737851
You need to log in before you can comment on or make changes to this bug.