Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120530 Firefox/14.0a2 BuildID: 20120530042008 STR: 1. Launch Firefox. 2. Load any website in the browser (e.g. https://www.google.ro/). 3. Right-click on any item on the page and select "Inspect Element" (or press 4. Ctrl+Shift+I/Cmd+Alt+I and select an item on the page). 5. Click on the "Node Operations" button (triangle facing down). 6. Click "Delete Node". 7. Repeat steps 5 and 6 until deleting the "html" node. 8. Click on the "Select element with mouse" button and select "tabbrowser#content". Delete this node too. After step 7, "undefined" is displayed as a node. When the user tries to select another item, only "tabbrowser#content" is available. After the user deletes this element, the browser becomes mostly unusable: all its features that use tabbed browsing become unresponsive (the user can't open/close tabs, move to already open tabs etc). I don't already have a regression range for this issue, but I will try to add one tomorrow.
Last good nightly: 2012-04-13 First bad nightly: 2012-04-14 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=10622eaff4fc&tochange=364f0a5a1d2d This issue also reproduces on the latest Nightly and Aurora builds (2012-06-01).
Seems to be a serious enough regression, did we want to track for Firefox 14?
Observation : After reproducing this issue, if a new window is opened, bookmark toolbar is missing.
Tracking for 14 although this would not block release of 14.
tracking 15 as well. we'll want it everywhere, if possible.
This patch looks reasonable. I wonder if we want a stricter comparison on doc != this.chromeDoc (!== ? ! === ?)? to allow highlighting chrome in content. Maybe not necessary. I'm currently having an issue highlighting chrome://browser/content/browser.xul in my nightly. Investigating that.
Comment on attachment 631334 [details] [diff] [review] v1 [Approval Request Comment] User impact if declined: user can break firefox Testing completed (on m-c, etc.): on m-c Risk to taking this patch (and alternatives if risky): small patch String or UUID changes made by this patch: nope
Comment on attachment 631334 [details] [diff] [review] v1 [Triage Comment] Patch looks low enough risk for Aurora, given where we are in the cycle.
Comment on attachment 631334 [details] [diff] [review] v1 [Approval Request Comment] Bug caused by (feature/regressing bug #): User impact if declined: user can break firefox Testing completed (on m-c, etc.): m-c Risk to taking this patch (and alternatives if risky): small amount of code String or UUID changes made by this patch: no
Comment on attachment 631334 [details] [diff] [review] v1 Looks fine for this next beta, please update status flags once landed.
Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0 Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20100101 Firefox/14.0 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20100101 Firefox/14.0 This seems to be fixed on Firefox 14 beta 11 (even if I don't see any patch landed in the bug)- the Inspector does not allow the user to remove tabbed browsing, but shouldn't the "Delete node" option for the "html" node be grayed out to avoid user confusion? Should I file a new bug for this?
> Should I file a new bug for this? Yes please.
Filed Bug 772371. Thank you Paul.
Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20100101 Firefox/15.0 Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20100101 Firefox/15.0 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20100101 Firefox/15.0 Verified on Firefox 15 beta 3 that removing tabbed browsing is not allowed. Verified using the STR from the Description on Windows 7, Ubuntu 12.04 and Mac OS X 10.6.