Open
Bug 1953168
Opened 10 days ago
Updated 2 days ago
edit html remove body node on new blank window
Categories
(DevTools :: Inspector, defect, P3)
Tracking
(Not tracked)
NEW
People
(Reporter: rurounitiagokun, Unassigned)
References
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:135.0) Gecko/20100101 Firefox/135.0
Steps to reproduce:
- change about:config setting browser.startup.homepage to about:blank
- open new window (not new tab, must be new window)
- open DOM inspector
- right click on body, select edit as html
- add anything inside body, can be a single character or a tag
- click outside the edit box
Actual results:
the body node disappear
Expected results:
to have the edited content applied in the body
Note:
- new blank tabs still works and don't reproduce the bug
- new window but forcing to load about:blank page directly still works and don't reproduce the bug
- right click on body and create new node still works and don't reproduce the bug
- using the script console to change the document.body.innerHTML='something' still works and don't reproduce the bug
- adding a new node inside body and editing this node instead of the body still works and don't reproduce the bug
- I also tested with version 136 and it still happens
Comment 1•10 days ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::DOM: Core & HTML' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Component: Untriaged → DOM: Core & HTML
Product: Firefox → Core
Updated•8 days ago
|
Component: DOM: Core & HTML → Inspector
Product: Core → DevTools
Comment 2•2 days ago
|
||
Thanks for the report, we can reproduce on 136 and 137, but not in Niightly (138).
I will check if this is a preference issue by doing a beta simulation. Otherwise no idea what would have fixed this.
Flags: needinfo?(jdescottes)
Comment 3•2 days ago
|
||
Looks like this was fixed with Bug 1665474.
We should probably add a test.
Updated•2 days ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in
before you can comment on or make changes to this bug.
Description
•