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

Issue 597435 link

Starred by 3 users
Status: Archived
Owner:
einbinder@chromium.org
Closed: Oct 31
Cc:
█ lushnikov@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Sources Pane: Sources viewing/editing area is covered with blank space at the top

Reported by arevin...@gmail.com, Mar 23 2016 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36

Steps to reproduce the problem:
Not sure if these steps matter, my problem is transient.
1. Using webpack and devtool: DEBUG && "cheap-module-eval-source-map" source map generation option
2. Step through several files of code

What is the expected behavior?
Each source is shown on the source pane from topmost rim. If you scroll down, the line numbers appearing at the top correspond the line numbers you see.

What went wrong?
A blank area several lines high with a line #1 tag persistently appears at the top. When you scroll, it stays, covering the scrolled text.

Did this work before? Yes Before my Chrome received updates. I.e. earlier than 49.0.2326.

Chrome version: 49.0.2623.87  Channel: stable
OS Version: OS X 10.11.3
Flash Version: Shockwave Flash 21.0 r0

The source's path, as appeared when you hever over its tab, is: webpack:///./~/babel-polyfill/~/core-js/modules/es6.promise.js?e8d6

Just if it might help.
Screen Shot 2016-03-24 at 01.44.46.png
149 KB View Download
Screen Shot 2016-03-24 at 01.45.48.png
156 KB View Download

Comment 1 by arevin...@gmail.com, Mar 23 2016 

The blank area stays once it appears and can be seen on all file tabs.

Comment 2 by arevin...@gmail.com, Mar 23 2016 

Just to be clear, this area is not visible from the beginning (see the attachment). It takes some stepping through for it to appear. It takes closing and opening the Dev Tools again to get rid of it for some time.
Screen Shot 2016-03-24 at 02.16.00.png
124 KB View Download

Comment 3 by gpbellav...@gmail.com, Mar 29 2016 

Confirmed on OSX 51.0.2693.0 canary (64-bit)

Comment 4 by arevin...@gmail.com, Mar 29 2016 

It is still an issue for the OSX 49.0.2623.110 (64bit).

I changed sourcemap generation from 'cheap-module-eval-source-map' to 'eval' - and nothing has improved.

Sometimes the bug looks like this (see attachment).
Screen Shot 2016-03-29 at 23.13.34.png
49.8 KB View Download

Comment 5 by arevin...@gmail.com, Mar 29 2016

Screen Shot 2016-03-29 at 23.18.36.png
46.2 KB View Download

Comment 6 by arevin...@gmail.com, Mar 29 2016 

And when no source file is open:
Screen Shot 2016-03-29 at 23.39.54.png
69.9 KB View Download

Comment 7 by kozyatinskiy@chromium.org, Mar 29 2016

Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)
Andrey, please take a look!

Comment 8 by lushnikov@chromium.org, Oct 8 2016

Cc: lushnikov@chromium.org
Labels: Needs-Feedback
Owner: einbinder@chromium.org
Is this still relevant? We've rolled codemirror a few times - does anyone experience this on the Chrome Canary?

Comment 9 by dgozman@chromium.org, Oct 31

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