Closed Bug 819140 Opened 13 years ago Closed 10 years ago

doesn't work when "Always use private browser mode" enabled and "Never remember history" is set

Categories

(Firefox :: Private Browsing, defect)

Product:
Firefox
Component:
Private Browsing
Version:
16 Branch
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: lorlarz, Unassigned)

Details

(Keywords: regression, Whiteboard: [invalid?])

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20100101 Firefox/16.0 Build ID: 20121024073032 Steps to reproduce: For the 2nd time, mozilla has screwed up my perfectly good app: http://tinyurl.com/ckn6p8w What did U do to mess it up this time? U changes with standard the first time. What happened now?? Did the standard change AGAIN??? U can view the Chrome version at http://tinyurl.com/7q42qzb to see how it worked before. Please let's keep some backward compat Mozillla. This is the 2nd time Mozilla has failed to provide backward compat. for the SAME app. Teachers who use my stuff, distrust. Actual results: shows some alert with undefined in it twice. Expected results: U can view the Chrome version at http://tinyurl.com/7q42qzb to see how it worked before.
Complaining doesn't help and you should instead add technical details. What are the steps to reproduce ? What are you doing step by step, what happens and what should happen ?
Flags: needinfo?(lorlarz)
I told you how you could see it running correctly on Chrome: Repeating: U can view the Chrome version at http://tinyurl.com/7q42qzb And, I told you the present result (onload): shows some alert with undefined in it twice.
Flags: needinfo?(lorlarz)
The two elements (formbox and databoxx) that you want to be side-by-side are too wide to fit inside their parent element (the <td>). Right-click on databoxx (the box you want to be on the right) and click "Inspect Element". You'll see its width in the inspector. If you make it just a little smaller, like 745px instead of 750px you'll see it shows up side-by-side. Dave
Oh, I thought you wanted the boxes to show up right. It sounds like you're upset about something else. What do you actually have to *do* in the page to get the alert box to show up? You need to give a *full, detailed* set of steps in order for us to help you. Dave
Happens right away when app loads -- with me doing nothing.
I can't reproduce the behavior you describe. I've tried it in the latest Firefox Nightly build, Firefox 17.0.1 (the current full release of Firefox), Firefox 16.0.2, and Firefox 16.0 (which is the version your report says). In each case there's no alert at all. Dave
Reporter emailed me privately that he can't remember his Bugzilla password and was blocked for guessing wrong too many times. Apparently there are more steps to reproduce but he still hasn't explained them. Dave
Please don't assume that other people can reproduce your issue. That's the reason why a detailed description of the issue is required. I don't get an alert with Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20100101 Firefox/17.0 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20100101 Firefox/20.0 SeaMonkey/2.17a1 I noticed that you are using Firefox16 Could yu please upgrade to Firefox 17 and test again. In case you still get the error you should try it in the Firefox safemode. http://support.mozilla.org/en-US/kb/Safe+Mode
He's privately emailed me that his private email suggesting that I start using his app was *not* the issue, but that it really is just on first load that alert boxes show up for him. He also privately emailed me that he updated to 17.0.1 and still sees the unexpected behavior--which, IIUC, is that two alert boxes pop up with the message "undefined". I cannot reproduce in any number of versions of Firefox on my mac. Dave
It's apparently one alert box with the message: Error: undefined undefined I'm giving up; I can't reproduce and I don't have time for this. And I can't submit every private email Brad sends me into this bug. If someone wants to help him get unblocked and logged into Bugzilla that'd be great. Thanks, Dave
Either the safemode or a new profile should "fix" the error or we would be able to reproduce it.
From Brad: """ I found a way to fix it, but it does not make me happy. If I go to the Privacy tab and set "Firefox will use custom settings for history" INSTEAD of "Never Remember History" (which used to be JUST FINE, as a setting) and I set: Accept cookies from site and 3rd party cookies until I close Firefox, the old data from way back reappear and all works (no Alert problems or any other). BUT: such settings should not be necessary. """ Dave
""" When you switch to "Never Remember History" funny things happen. When you switch back to "Custom settings for History" the browser, by itself, has checked "Always Use Private Browsing" as well as the 2 accept cookies checkboxes (which is maybe what it is secretly doing with "Never Remember History"), THEN : ALL THE PROBLEMS (the alert and lack of functionality) re-appear. This is what has changed in versions 16 on in Firefox which are screwed-up. Sorry to take so much of your time. Please inform the others. This IS a FF problem (bug). """ Dave
Severity: normal → major
This error is major for people using new data storage capability that new browsers have, and as accessed via JavaScript. This same problem making things go for functioning to non-functioning could have happened to other users of other similar apps -- and some of these apps could be very important. Think about it.
Component: Untriaged → Layout: Form Controls
Product: Firefox → Core
Component: Layout: Form Controls → Untriaged
Product: Core → Firefox
I'm not seeing the "undefined" error either, but I am getting the following error messages in the error console when opening this app: Timestamp: 12/11/2012 5:41:25 PM Error: The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol. Source File: http://nottoolate.info/mydbx/doAll.html?a=your_col_1&b=your_col_2&c=your_col_3&d=your_col_4&e=your_col_5&f=your_col_6&g=your_col_7&h=your_col_8 Line: 0 Timestamp: 12/11/2012 5:41:25 PM Error: Image corrupt or truncated: <unknown> Source File: <unknown> Line: 0 I'm also getting numerous warnings when actually using the app. lorlarz, could you please open the Error Console while using your app (Ctrl+Shift+J) and take a look at those warnings? They might help you solve your problem
I can make it so I do not have a problem, and I already told you so IN DETAIL. I HAVE ALSO CLEARLY INDICATED HOW TO MAKE THE PROBLEM HAPPEN (and will do so again below) AND clearly demonstrate it is a Mozilla (FF) browser versions 16-17 problem . The problem came up in the first place when YOUR browser, versions 16 on, started under the Privacy tab started AUTOMATICALLY checking "Always use private browser mode" WHEN "Never remember history" is selected from the main drop-down (whether selected in the present or in the past by a user of an older, just updated, browser). OLDER VERSIONS DO NOT DO THIS. Thus, my program was running perfectly with "Never remember history" set by users UNTIL their browsers were updated to version 16 or 17. [ THIS IS A CLEARLY REPRODUCIBLE PROBLEM WHICH I HAVE NOW TWICE TOLD YOU HOW TO REPRODUCE, again. ] There is a solution, BUT users should NOT have had to turn to this solution (and the browsers should have remained operational, like version earlier than ver. 16 with any update to version 16 or later). Anyhow, once you make the problem (and make the alert "undefined undefined" come up _and_ the program not running at all _BY_ setting the Privacy setting to "Never remember history") and thus verify the problem, you can subsequently FIX this problem (and not have any problems with the alert OR the program) if you: switch to "Use custom setting for browsing" and do not set the first checkbox. OUTSIDE OF THAT: Perhaps any other combination works as long as the first "Always use private browser mode" checkbox is not checked (though I will leave YOU to try all combinations) ; I happen to check fourth and sixth of all the checkboxes shown and have NO PROBLEMS WITH ALERT OR ANY OTHER PROBLEMS RUNNING THE PROGRAM, with the "Always use private browser mode" UNCHECKED. In this information I have given you is THE BUG (and it is your, Mozilla): Do NOT be setting (automatically) "Always use private browser mode" when "Never remember history" is selected. THIS IS THE PROBLEM. It is a FF ver 16 & 17 BUG.
Re-edited and slightly amended for clarity or emphasis: I can make it so I do not have a problem, and I already told you how to do so IN DETAIL. I HAVE ALSO CLEARLY INDICATED HOW TO MAKE THE PROBLEM HAPPEN (and will do so again below) AND clearly demonstrate it is a Mozilla (FF) browser versions 16-17 problem . The problem came up in the first place when YOUR browser, versions 16 on, under the Privacy tab started AUTOMATICALLY checking "Always use private browser mode" WHEN "Never remember history" is selected from the main drop-down (whether "Never remember history" is selected in the present or OR WAS _in the past_ by a user of an older, just-updating his/her browser). OLDER VERSIONS DO NOT DO THIS (on update). Thus, my program was running perfectly with "Never remember history" set by users UNTIL their browsers were updated to version 16 or 17. [ THIS IS A CLEARLY REPRODUCIBLE PROBLEM WHICH I HAVE NOW TOLD YOU HOW TO REPRODUCE, YET again. ] There is a solution, BUT users should NOT have had to turn to this solution (and the browsers should have remained operational, like versions earlier being updated to versions earlier than ver. 16-17 DID) . Anyhow, once you make the problem (and make the alert "undefined undefined" come up _and_ the program not running at all _BY_ setting the Privacy setting to "Never remember history") and thus verify the problem, you can subsequently FIX this problem (and not have any problems with the alert OR the program) if you: switch to "Use custom setting for browsing" and do not set the first checkbox. OUTSIDE OF THAT: Perhaps any other combination works as long as the first "Always use private browser mode" checkbox is not checked (though I will leave YOU to try all combinations) ; I happen to check fourth and sixth of all the checkboxes shown and have NO PROBLEMS WITH ALERT OR ANY OTHER PROBLEMS RUNNING THE PROGRAM (with the "Always use private browser mode" UNCHECKED)). In this information I have given you is THE BUG (and it is yours, Mozilla): Do NOT be setting (automatically) "Always use private browser mode" when "Never remember history" is selected. THIS IS THE PROBLEM. It is a FF ver 16 & 17 BUG. In short: Loss of functionality which need not and should not occurs when people simply updates a FF browser older than version 16 TO version 16 or above -- the disfunctionality happens automatically (given the user has a certain very ok and appropriate setting, "Never Remember History") and IS NOT USER ERROR (NOR is what happens appropriate or reasonable). For more than one reason the bug should be fixed.
Instead of fixing the problem, you have made it so when Firefox updates (which it does automaticaly for many), the "Always use private browing mode" (under the Privacy tab) always gets set TO CHECKED which disables indexedDB functionality. Because the updates are automatic for many people, they do not know when their indexedDB functionality will drop off -- nor will sites providing stored data know when their clients no longer have the functionality OR will unexpectedly find they do not have it. At least you should HONOR USER SETTINGS AND not set "Always use private browing mode" _BACK_ to CHECKED !! (Moreover, it is debatable that "Always use private browing mode" should mean disabling indexedDB functionality OR that disabling indexedDB functionality should be the default). You also screwed-up in a new way: I cannot get the new Firefox 18.0 to save the setting "Clear History when Firefox closes" (also under the Privacy tab). Each time I close the browser, I find this UNCHECKED, thoug I checked it.
Also: The Firefox browser was, uncharacteristically, crashing repeatedly. I had to uninstall and reinstall it, to get at least some improvement. (This is the third of three problems I am siting -- though this one I can no longer provide specifics on. I vote for you to work on the original problem mainly and take note of the second one I mentioned, after that.) I will provide specifics if I get more repeated crashing.
Are comment 13 and comment 14 still required to reproduce the problem?
Flags: needinfo?(lorlarz)
Did they make it so the program does not work again, even with the work-around (for certain common or default settings changed)?? Let me know, I do not constantly check on things and change all privacy things to check if programs keep working. Do let me know (and let me know if you have found browser settings that allow it to work, like I have in the past).
Flags: needinfo?(lorlarz)
Thanks for the update. Impossible to tell you if you will continue to crash, because you never identified the crash. Personally, I'm not going to try testing further because I fail to see how to reproduce the issue. It's possible the change in behavior was deliberate by developers. Getting this in proper component a long time ago might have helped get resolution sooner.
Component: Untriaged → Private Browsing
Keywords: regression
Summary: 2nd time you made the same app stop running → doesn't work when "Always use private browser mode" enabled and "Never remember history" is set
Whiteboard: [closeme 2014-07-01][invalid?]
Dear Wayne Mary, I did my absolute best describing the problem with the program ( the program at http://nottoolate.info/mydb/doAll.html?a=your_col_1&b=your_col_2&c=your_col_3&d=your_col_4&e=your_col_5&f=your_col_6&g=your_col_7&h=your_col_8 ) I did my personal best to describe the problem in previous posts here and also I found a solution that, in the past, worked and described that. I tested the thing just now. The program (with privacy settings loosened as much as one would be inclined to) now does not work in either FF or Chrome. The present description of the problem (which should be reproducible) is: now the program does nothing. When you add a record (per the instructions) nothing is added (thus nothing is displayed -- right away or in subsequent visits). I would much appreciate a fix to this. The relevant JS file is at: http://nottoolate.info/mydbx/myindexedn3.js If you figure a fix, let me know!! Thanks. Regards, Brad
Now, via experimentation, the program is back to giving an alert: "undefined, undefined" IN ALL MODERN BROWSERS (IE, FF, and Chrome, anyway). Plus Firebug, in addition, says: nvalidStateError: A mutation operation was attempted on a database that did not allow mutations. RE: line 129 var mytransaction = db.transaction(['mytablexBxB'], "readwrite"); Is this an improvement or not??? Anyhow, it is something other than no browser response at all (and this error is NOW in all browsers !!). Know that http://nottoolate.info/mydbx/myindexedn3.js (which is behind the program at: http://nottoolate.info/mydb/doAll.html?a=your_col_1&b=your_col_2&c=your_col_3&d=your_col_4&e=your_col_5&f=your_col_6&g=your_col_7&h=your_col_8 ) has now been altered since the earlier Comments I made just today. I have been trying things. I guess I do not know how to allow the database to "accept mutations"; I apparently only know how to make TABLE readwrite !!!
Whiteboard: [closeme 2014-07-01][invalid?] → [invalid?]
Closing per note: Phoenix - Updated • 2 years ago Whiteboard: [closeme 2014-07-01][invalid?] → [invalid?]
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.