(In reply to :Gijs (he/him) from comment #19) > I suspect this is an issue with xulstore or the browser.xul -> .xhtml rename. I don't think anything in this patch itself could possibly trigger this issue... Can you reproduce on a clean profile? What about now-current nightly? Are you reusing a profile between "regular" nightly and the custom build otherwise, and could that be the cause of the issue? When I last tested (amd commented in comment 14), I overwrited the `C:\Program Files\Firefox Nightly` contents with the files in the zip file from comment 13, created a clean profile and there I saw this issue. Now, I just ran the `firefox.exe` along with the other extracted files with a clean profile, and I can't reproduce it now. So.. false alarm, I guess?
Bug 1543508 Comment 20 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to :Gijs (he/him) from comment #19) > I suspect this is an issue with xulstore or the browser.xul -> .xhtml rename. I don't think anything in this patch itself could possibly trigger this issue... Can you reproduce on a clean profile? What about now-current nightly? Are you reusing a profile between "regular" nightly and the custom build otherwise, and could that be the cause of the issue? When I last tested (and commented in comment 14), I overwrited the `C:\Program Files\Firefox Nightly` contents with the files in the zip file from comment 13, created a clean profile and there I saw this issue. Now, I just ran the `firefox.exe` along with the other extracted files with a clean profile, and I can't reproduce it now. So.. false alarm, I guess?