New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 666946 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit 29 days ago
Closed: Nov 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

DevTools: LiveSASS experiment is broken

Project Member Reported by lushnikov@chromium.org, Nov 18 2016

Issue description

On all platforms, on tip-of-tree: 57.0.2925.0
 
It turned out that LiveSASS doesn't work for the chromium with "--debug-devtools" flag. The reason is that worker's front-end is not getting debugDevtools queryParam.
It's broken for me on 57.0.2925.0 (MacOS Sierra 10.12) and I'm not using the --debug-devtools flag. Here's a quick video: https://www.youtube.com/watch?v=TGCW23iB2Wo
Project Member

Comment 3 by bugdroid1@chromium.org, Nov 21 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/178617ce268c8d8e5a19f46e43d239b76a117752

commit 178617ce268c8d8e5a19f46e43d239b76a117752
Author: lushnikov <lushnikov@chromium.org>
Date: Mon Nov 21 21:30:06 2016

DevTools: launch worker runtimes with all the queryParams of the main page runtime.

In order to properly load modules, Runtime relies on a few queryParam flags.
One of them, remoteBase, was successfully passed to the worker runtimes.
Another one, debugFrontend, wasn't.

As a result, the remote modules were not loaded properly in workers for
the debugDevtools front-ends.

This patch passes all the queryParams to the worker runtime.

BUG= 666946 
R=dgozman

Review-Url: https://codereview.chromium.org/2516833002
Cr-Commit-Position: refs/heads/master@{#433656}

[modify] https://crrev.com/178617ce268c8d8e5a19f46e43d239b76a117752/third_party/WebKit/Source/devtools/front_end/Runtime.js
[modify] https://crrev.com/178617ce268c8d8e5a19f46e43d239b76a117752/third_party/WebKit/Source/devtools/front_end/common/Worker.js

Hey Dave,

That's weird. Is there anything in the console (liveSASS reports its failures in console)? Could you please also open devtools-on-devtools and check errors there as well? (how to open devtools-on-devtools: https://coderwall.com/p/0m4hqa/chrome-devtools-inception)
Dave, any updates on this?
Status: WontFix (was: Assigned)
LiveSASS experiment has been removed. See  crbug.com/782935 

Sign in to add a comment