DevTools: liveSASS should tolerate race between iNotify and BrowserSync

DevTools: liveSASS should tolerate race between iNotify and BrowserSync

In a specific setup, with BrowserSync, SASS watchdog and
DevTools Workspaces, there's a race between iNotify and BrowserSync.
Both are pushing updated StyleSheet into inspected page.

The problem here is that BrowserSync also uses a cache-busting URL for
the stylesheet, appending "?rel=<timestamp>" to stylesheet URL.

As a result, the following sequence of events takes place:
1. As SCSS file is updated on file system, watchDog picks up changes and
   produces new CSS files
2. BrowserSync streamlines new CSS into inspected page, with a cache-busting
   URL
3. DevTools start loading new SourceMap for the StyleSheet
4. At this moment, DevTools Workspace realizes CSS file changes and updates
   style sheets one more time. The stylesheet with a specific cache-busted URL
   goes away.
5. LiveSASS tries to fetch content for original StyleSheet with cache-busting
   URL (which was already removed) and fails.

Nevertheless, the LiveSASS should not be affected with
this race condition - both BrowserSync and iNotify push
the same content.

This patch stops relying on StyleSheet URL and starts looking for styleSheets
which refer to the sourceMap.

BUG=608106
R=dgozman, pfeldman

Committed: https://crrev.com/ee0c104c20b4dd17f1f6ae00b1d09c88236ebda9
Cr-Commit-Position: refs/heads/master@{#393127}

[lushnikov, 2016-05-11 18:30:24]

please, take a look!

[lushnikov, 2016-05-11 22:22:40]

Description was changed from

==========
DevTools: create editable SourceMap even for URL's with cache-busting

In case of browser sync, the style sheet injection happens twice: once
with a plain URL, and second time with cache-busting url with suffix
"?rel=<timestamp>".

This patch makes LiveSASS support this case.

BUG=none
R=dgozman, pfeldman
==========

to

==========
DevTools: liveSASS should tolerate race between iNotify and BrowserSync

In a specific setup, with BrowserSync, SASS watchdog and
DevTools Workspaces, there's a race between iNotify and BrowserSync.
Both are pushing updated StyleSheet into inspected page.

The problem here is that BrowserSync also uses a cache-busting URL for
the stylesheet, appending "?rel=<timestamp>" to stylesheet URL.

As a result, the following sequence of events takes place:
1. As SCSS file is updated on file system, watchDog picks up changes and
   produces new CSS files
2. BrowserSync streamlines new CSS into inspected page, with a cache-busting
   URL
3. DevTools start loading new SourceMap for the StyleSheet
4. At this moment, DevTools Workspace realizes CSS file changes and updates
   style sheets one more time. The stylesheet with a specific cache-busted URL
   goes away.
5. LiveSASS tries to fetch content for original StyleSheet with cache-busting
   URL (which was already removed) and fails.

Nevertheless, the LiveSASS should not be affected with
this race condition - both BrowserSync and iNotify push
the same content.

This patch stops relying on StyleSheet URL and starts looking for styleSheets
which refer to the sourceMap.

BUG=none
R=dgozman, pfeldman
==========

[lushnikov, 2016-05-11 22:23:27]

Description was changed from

==========
DevTools: liveSASS should tolerate race between iNotify and BrowserSync

In a specific setup, with BrowserSync, SASS watchdog and
DevTools Workspaces, there's a race between iNotify and BrowserSync.
Both are pushing updated StyleSheet into inspected page.

The problem here is that BrowserSync also uses a cache-busting URL for
the stylesheet, appending "?rel=<timestamp>" to stylesheet URL.

As a result, the following sequence of events takes place:
1. As SCSS file is updated on file system, watchDog picks up changes and
   produces new CSS files
2. BrowserSync streamlines new CSS into inspected page, with a cache-busting
   URL
3. DevTools start loading new SourceMap for the StyleSheet
4. At this moment, DevTools Workspace realizes CSS file changes and updates
   style sheets one more time. The stylesheet with a specific cache-busted URL
   goes away.
5. LiveSASS tries to fetch content for original StyleSheet with cache-busting
   URL (which was already removed) and fails.

Nevertheless, the LiveSASS should not be affected with
this race condition - both BrowserSync and iNotify push
the same content.

This patch stops relying on StyleSheet URL and starts looking for styleSheets
which refer to the sourceMap.

BUG=none
R=dgozman, pfeldman
==========

to

==========
DevTools: liveSASS should tolerate race between iNotify and BrowserSync

In a specific setup, with BrowserSync, SASS watchdog and
DevTools Workspaces, there's a race between iNotify and BrowserSync.
Both are pushing updated StyleSheet into inspected page.

The problem here is that BrowserSync also uses a cache-busting URL for
the stylesheet, appending "?rel=<timestamp>" to stylesheet URL.

As a result, the following sequence of events takes place:
1. As SCSS file is updated on file system, watchDog picks up changes and
   produces new CSS files
2. BrowserSync streamlines new CSS into inspected page, with a cache-busting
   URL
3. DevTools start loading new SourceMap for the StyleSheet
4. At this moment, DevTools Workspace realizes CSS file changes and updates
   style sheets one more time. The stylesheet with a specific cache-busted URL
   goes away.
5. LiveSASS tries to fetch content for original StyleSheet with cache-busting
   URL (which was already removed) and fails.

Nevertheless, the LiveSASS should not be affected with
this race condition - both BrowserSync and iNotify push
the same content.

This patch stops relying on StyleSheet URL and starts looking for styleSheets
which refer to the sourceMap.

BUG=608106
R=dgozman, pfeldman
==========

[lushnikov, 2016-05-11 22:23:36]

The CQ bit was checked by lushnikov@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-05-11 22:24:05]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1965223003/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1965223003/20001

[commit-bot: I haz the power, 2016-05-12 00:13:17]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-05-12 00:13:18]

Dry run: This issue passed the CQ dry run.

[dgozman, 2016-05-12 01:00:01]

lgtm, but we should follow-up with removing of compiledURL() completely.

[lushnikov, 2016-05-12 01:05:16]

The CQ bit was checked by lushnikov@chromium.org

[commit-bot: I haz the power, 2016-05-12 01:05:40]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1965223003/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1965223003/20001

[commit-bot: I haz the power, 2016-05-12 01:10:15]

Description was changed from

==========
DevTools: liveSASS should tolerate race between iNotify and BrowserSync

In a specific setup, with BrowserSync, SASS watchdog and
DevTools Workspaces, there's a race between iNotify and BrowserSync.
Both are pushing updated StyleSheet into inspected page.

The problem here is that BrowserSync also uses a cache-busting URL for
the stylesheet, appending "?rel=<timestamp>" to stylesheet URL.

As a result, the following sequence of events takes place:
1. As SCSS file is updated on file system, watchDog picks up changes and
   produces new CSS files
2. BrowserSync streamlines new CSS into inspected page, with a cache-busting
   URL
3. DevTools start loading new SourceMap for the StyleSheet
4. At this moment, DevTools Workspace realizes CSS file changes and updates
   style sheets one more time. The stylesheet with a specific cache-busted URL
   goes away.
5. LiveSASS tries to fetch content for original StyleSheet with cache-busting
   URL (which was already removed) and fails.

Nevertheless, the LiveSASS should not be affected with
this race condition - both BrowserSync and iNotify push
the same content.

This patch stops relying on StyleSheet URL and starts looking for styleSheets
which refer to the sourceMap.

BUG=608106
R=dgozman, pfeldman
==========

to

==========
DevTools: liveSASS should tolerate race between iNotify and BrowserSync

In a specific setup, with BrowserSync, SASS watchdog and
DevTools Workspaces, there's a race between iNotify and BrowserSync.
Both are pushing updated StyleSheet into inspected page.

The problem here is that BrowserSync also uses a cache-busting URL for
the stylesheet, appending "?rel=<timestamp>" to stylesheet URL.

As a result, the following sequence of events takes place:
1. As SCSS file is updated on file system, watchDog picks up changes and
   produces new CSS files
2. BrowserSync streamlines new CSS into inspected page, with a cache-busting
   URL
3. DevTools start loading new SourceMap for the StyleSheet
4. At this moment, DevTools Workspace realizes CSS file changes and updates
   style sheets one more time. The stylesheet with a specific cache-busted URL
   goes away.
5. LiveSASS tries to fetch content for original StyleSheet with cache-busting
   URL (which was already removed) and fails.

Nevertheless, the LiveSASS should not be affected with
this race condition - both BrowserSync and iNotify push
the same content.

This patch stops relying on StyleSheet URL and starts looking for styleSheets
which refer to the sourceMap.

BUG=608106
R=dgozman, pfeldman
==========

[commit-bot: I haz the power, 2016-05-12 01:10:16]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-05-12 01:14:20]

Description was changed from

==========
DevTools: liveSASS should tolerate race between iNotify and BrowserSync

In a specific setup, with BrowserSync, SASS watchdog and
DevTools Workspaces, there's a race between iNotify and BrowserSync.
Both are pushing updated StyleSheet into inspected page.

The problem here is that BrowserSync also uses a cache-busting URL for
the stylesheet, appending "?rel=<timestamp>" to stylesheet URL.

As a result, the following sequence of events takes place:
1. As SCSS file is updated on file system, watchDog picks up changes and
   produces new CSS files
2. BrowserSync streamlines new CSS into inspected page, with a cache-busting
   URL
3. DevTools start loading new SourceMap for the StyleSheet
4. At this moment, DevTools Workspace realizes CSS file changes and updates
   style sheets one more time. The stylesheet with a specific cache-busted URL
   goes away.
5. LiveSASS tries to fetch content for original StyleSheet with cache-busting
   URL (which was already removed) and fails.

Nevertheless, the LiveSASS should not be affected with
this race condition - both BrowserSync and iNotify push
the same content.

This patch stops relying on StyleSheet URL and starts looking for styleSheets
which refer to the sourceMap.

BUG=608106
R=dgozman, pfeldman
==========

to

==========
DevTools: liveSASS should tolerate race between iNotify and BrowserSync

In a specific setup, with BrowserSync, SASS watchdog and
DevTools Workspaces, there's a race between iNotify and BrowserSync.
Both are pushing updated StyleSheet into inspected page.

The problem here is that BrowserSync also uses a cache-busting URL for
the stylesheet, appending "?rel=<timestamp>" to stylesheet URL.

As a result, the following sequence of events takes place:
1. As SCSS file is updated on file system, watchDog picks up changes and
   produces new CSS files
2. BrowserSync streamlines new CSS into inspected page, with a cache-busting
   URL
3. DevTools start loading new SourceMap for the StyleSheet
4. At this moment, DevTools Workspace realizes CSS file changes and updates
   style sheets one more time. The stylesheet with a specific cache-busted URL
   goes away.
5. LiveSASS tries to fetch content for original StyleSheet with cache-busting
   URL (which was already removed) and fails.

Nevertheless, the LiveSASS should not be affected with
this race condition - both BrowserSync and iNotify push
the same content.

This patch stops relying on StyleSheet URL and starts looking for styleSheets
which refer to the sourceMap.

BUG=608106
R=dgozman, pfeldman

Committed: https://crrev.com/ee0c104c20b4dd17f1f6ae00b1d09c88236ebda9
Cr-Commit-Position: refs/heads/master@{#393127}
==========

[commit-bot: I haz the power, 2016-05-12 01:14:21]

Patchset 2 (id:??) landed as
https://crrev.com/ee0c104c20b4dd17f1f6ae00b1d09c88236ebda9
Cr-Commit-Position: refs/heads/master@{#393127}