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

Issue 760823 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
kojii@chromium.org
█ dominicc@chromium.org
domenic@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Custom element errors do not report where it occurred correctly when constructor returned an invalid value

Project Member Reported by kojii@chromium.org, Aug 31 2017 
adamk@ tested various cases in  issue 639739  and figured out that exceptions no longer point to the constructor. It points to defineElement in upgrade, or the top of HTML file the element occurred in non-upgrade.
https://bugs.chromium.org/p/chromium/issues/detail?id=639739#c21
https://chromium-review.googlesource.com/c/chromium/src/+/629299/6#message-58c564fdc734eee0c85c96d0eb592dfb977b8dfa

Comment 1 by dominicc@google.com, Aug 31 2017 

For that error about returning the wrong object, I'm not sure how we would point to the constructor. It would be ideal to point to the return statement because that's what needs to be fixed, but from an execution point of view, execution has moved on.

Comment 2 by kochi@chromium.org, Oct 16 2017

Status: Available (was: Untriaged)
Marking this available for someone to take a look.
Project Member

Comment 3 by sheriffbot@chromium.org, Oct 16

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by tkent@chromium.org, Oct 17

Labels: -Hotlist-Recharge-Cold
Status: Available (was: Untriaged)
►

Sign in to add a comment