Warn users that DOM Tree changes don't persist
Reported by
kaycebas...@gmail.com,
Nov 7 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3257.0 Safari/537.36 Steps to reproduce the problem: 1. Add a local repo to Workspaces 2.0 2. Make a change to the DOM via the Elements panel What is the expected behavior? Users receive some UI feedback indicating that changes made via the DOM Tree don't persist to disk. Instead, they should make changes via the Sources panel. What went wrong? No UI feedback Did this work before? No Chrome version: 64.0.3257.0 Channel: canary OS Version: OS X 10.12.6 Flash Version: Ideally this use-case works. But second-best scenario is to at least give loud and clear feedback that this is a known limitation.
,
Dec 13 2017
The thing is, the DOM has nothing to do with the original document; oftentimes, it's built with javascript. Its unlikely that this HTML should be saved to the filesystem. Regarding the error, we don't have any good UX to show this kind of errors. For now, there are no plans to come up with the one, so I'll close it for now unless there are more complaints. |
||
►
Sign in to add a comment |
||
Comment 1 by kozy@chromium.org
, Nov 7 2017Status: Assigned (was: Unconfirmed)