Jump to declaration for JavaScript debugging.
Reported by
tide...@gmail.com,
Dec 2 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 Steps to reproduce the problem: 1. Open sources panel and open any JavaScript file. 2. cmd+click on any function. 3. Jump to the function declaration in which file it belong to. What is the expected behavior? What went wrong? Not implement yet. Did this work before? N/A Chrome version: 62.0.3202.94 Channel: stable OS Version: OS X 10.12.6 Flash Version:
,
Dec 4 2017
This is a feature request ticket, not bug.
,
Dec 4 2017
Thank you for providing more feedback. Adding requester "mmanchala@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 6 2017
As per comment#2 considering this issue as Feature request. Hence marking as Untriaged. Thanks!
,
Dec 8 2017
,
Dec 12 2017
On pause you can highlight function and click by its source in popover to go to definition. Unfortunately in generic case not on pause it is hard to solve problem and we do not have enough resources to fix it in next year. We probably can try approach based on just search (e.g. sublime uses this heuristic) but it is not as precise and as powerful as jump to declaration. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by mmanchala@chromium.org
, Dec 4 2017Labels: Needs-Triage-M62 Needs-Feedback