"Go to Line..." does not work on view source after detach the view source tab
Categories
(Toolkit :: View Source, defect, P2)
Tracking
()
People
(Reporter: alice0775, Unassigned)
References
Details
| Reporter | ||
Updated•9 years ago
|
Comment 1•9 years ago
|
||
Comment 3•9 years ago
|
||
Updated•7 years ago
|
Comment 4•7 years ago
|
||
Comment 5•6 years ago
|
||
Is there any plan to actually fix this? This is making view-source pretty much completely unusable for me: I want to go to the line an error is on, but of course that does not work... I end up having to copy/paste things into an editor instead.
Redirecting to Patrick... I am not very active in this component at the moment. Maybe it should have a new triage owner?
Comment 7•6 years ago
|
||
Honza does the triage for view source these days. So forwarding to him.
Honza, would you mind filing the bug to change the triage owner to you?
Comment 8•6 years ago
|
||
(In reply to Patrick Brosset <:pbro> from comment #7)
Honza, would you mind filing the bug to change the triage owner to you?
Done
I'll keep NI to myself, to investigate this later.
Honza
Comment 9•6 years ago
|
||
I was debugging this quickly and the issue seems to be communication between the frame script and ViewSourceBrowser.
- Go to line menu action is implemented here:
https://searchfox.org/mozilla-central/rev/3366c3d24f1c3818df37ec0818833bf085e41a53/toolkit/components/viewsource/content/viewSource-content.js#747
It's based on sending a message
sendAsyncMessage("ViewSource:PromptAndGoToLine");
- The message should be handled by
ViewSourceBrowserhere:
https://searchfox.org/mozilla-central/rev/3366c3d24f1c3818df37ec0818833bf085e41a53/toolkit/components/viewsource/ViewSourceBrowser.jsm#113
But the handler is never executed.
I am setting P2, since this should be fixed and there are likely other messages not being handled properly.
Honza
Comment 10•3 years ago
|
||
I can't reproduce this anymore. I got this pushlog with mozregression --arg=https://bugzilla.mozilla.org/show_bug.cgi?id=1308049 --good 2021-06-16 --bad 2019-08-15 --find-fix. I assume bug 1505915 fixed this. Honza, what do you think?
Comment 11•3 years ago
|
||
I can confirm, this works for me in Fx 103 (Nightly) as well as in Fx 101 (Release). Tested on Win10
Thank you for the ping, Gregory.
Closing
Description
•