New issue
Advanced search Search tips

Issue 709277 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Oct 31
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

DevTools triggers change detection in separate file editor. Local files

Reported by trendal....@gmail.com, Apr 6 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1. Open JS source file in text editor (gedit)
2. Open the same mapped file in DevTools>Sources tab
3. Edit code in text editor (gedit), after some time it will detect changes to the source file and want you to reload.  

DevTools is not actually making any source changes that I can see, but it is somehow marking the file as edited which wiggs gedit out because it thinks it was changed outside of it's control.

What is the expected behavior?
DevTools should be able to open a file for viewing without triggering source changes.

What went wrong?
If you hit reload in your text editor, you of course lose all history of changes, which can be devastating if you rely on ctrl-z a lot (I do).

It seems to be worse when using break points in Javascript.

Did this work before? Yes Can't recall, several updates ago.

Chrome version: 56.0.2924.87  Channel: stable
OS Version: Mint 17
Flash Version: 

I only edit CSS in DevTools.  Not Javascript or HTML etc.  I'd like to be able to set DevTools to open all other files in read-only mode.  I want to be able to edit CSS and set break points in Javascript.  Without it messing up my text editor.
 
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)
After having gedit warn me I needed to reload, I've closed all files in DevTools>Sources tab but left DevTools open and continued coding in gedit.  In a few keystrokes, gedit warned me again that there has been changes made to the file and do I want to reload?

It seems to do it a number of times in a row, then is quiet for a while.
fail.png
101 KB View Download
Owner: einbinder@chromium.org
Joel, could you please take a look?
I am having trouble reproducing this. How long does it usually take for gedit to complain? If you leave DevTools open, but never interact with it do changes still appear?
I'm just noticing that I don't see this behaviour on my home computer.  It's running Mint 18 instead of 17.  Maybe I didn't give this due diligence in testing.

As far as timing, at work I leave gedit and chrome open for days or weeks at a time so I don't know from initial setup when it happens but I would say it comes around every 5 - 15 minutes very randomly.  Sometimes several times a minute.

I will try to find time to upgrade my work computer to Mint 18 and post back about the status.


Status: Archived (was: Assigned)
Bulk closing low-priority issues with no activity. Please re-file and refer to the closed issue if it's essential to fix.

Sign in to add a comment