User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0 ie, display of selected cities in weather.com. could be missing cookies. i have accept option on in firefox and i just downloaded your version 3. Reproducible: Always Steps to Reproduce: 1.open home page, notice display of data 2.re code, logo off 3.log on Actual Results: ok until the next time i log back on Expected Results: remembered how the data was from the last session
> notice display of data Ray, what exactly and specifically should QA and bug triaging people be looking for? Please be clear and specific. > re code, logo off What exactly are you trying to indicate here? ----- Note that the webpage itself has lots of coding issues and problems: - http://validator.w3.org/check?uri=http://www.optimum.net/optonline 163 validation markup errors - http://jigsaw.w3.org/css-validator/validator?uri=http://www.optimum.net/optonline 54 parsing errors - 33 <script>s declared! It would take considerable amount of time figuring out what each script functions do and for which browser and for which browser versions... - Lots of nested tables, overconstrained tables, clearly and definitely overconstrained ones - obvious signs of over-coded CSS code and declarations - etc.
This is a mass search for bugs which are in the Firefox General component, are UNCO, have not been changed for 500 days and have an unspecified version. Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.