New issue
Advanced search Search tips

Issue 605215 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Web Bluetooth DOMException on OSX displays as truncated info message

Project Member Reported by lgar...@chromium.org, Apr 20 2016

Issue description

Chrome 52.0.2713.0 
OSX 10.11.4
What steps will reproduce the problem?
(1) Visit https://permission.site
(2) Open the console.
(3) Click on "Bluetooth"
(4) Click on the info message.
(5) Scroll to the right of the message string.

What is the expected output?
francois.png (see [1]), with a wrapped message and a clickable link.

What do you see instead?
At step 3) lgarron-console-open-already.png
At step 4) off-screen.png
At step 5) off-screen-scrolled.png

If I swap steps 2 and 3, then I get lgarron-console-opened-later.png at step 3, where the string for the info message is not even visible.

Jeff, is this a known issue or a regression in just my build?

[1] https://github.com/GoogleChrome/permission.site/pull/12#issuecomment-212394516
 
francois.png
115 KB View Download
lgarron-console-opened-later.png
237 KB View Download
lgarron-console-open-already.png
238 KB View Download
off-screen.png
264 KB View Download
off-screen-scrolled.png
223 KB View Download
Status: WontFix (was: Assigned)
This is the difference between `console.info(new DOMException("Very long message Very long message Very long message Very long message Very long message Very long message Very long message Very long message", "NotFoundError"))` and `console.info([new DOMException("Very long message Very long message Very long message Very long message Very long message Very long message Very long message Very long message", "NotFoundError")])`. By passing "arguments" in displayOutcome(), you get the array version, which doesn't show the whole message by default. You can click the arrow to see the rest.
Oh, I see. There doesn't seem to be a nice way around it for what I'm trying to do (a single console call with a bunch of parts).

Thanks for the explanation.
For the record, jyasskin@ helped me figure out why I couldn't work around the problem, which is that `arguments` is not actually an array: https://github.com/GoogleChrome/permission.site/commit/f72ff0f169411b1a5b87ec0596c46af527c09bcb

Sign in to add a comment