Maybe something something like: > There is a known issue with `javascript:` bookmarklets in Firefox 68 due to a new, much faster, URL bar implementation that does not handle them correctly yet. See <https://bugzilla.mozilla.org/show_bug.cgi?id=1552141>. I don't know whether we should mention the turn-off pref for people who rely on javascript: bookmarklets for their daily work; I feel like we should, but then we'll get people stuck with quantumbar turned off like I did. :( Fwiw, I largely agree with comment 16 in terms of shipping with functionality regressions, unless we have really good data that the new implementation is much better for most users.
Bug 1552141 Comment 17 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Maybe something something like: > There is a known issue with triggering `javascript:` bookmarklets via bookmark keywords in Firefox 68 due to a new, much faster, URL bar implementation that does not handle them correctly yet. See <https://bugzilla.mozilla.org/show_bug.cgi?id=1552141>. I don't know whether we should mention the turn-off pref for people who rely on javascript: bookmarklets triggered via keyword for their daily work; I feel like we should, but then we'll get people stuck with quantumbar turned off like I did. :( Fwiw, I largely agree with comment 16 in terms of shipping with functionality regressions, unless we have really good data that the new implementation is much better for most users. This is somewhat mitigated by the fact that this really is an intersection of two somewhat-niche features (bookmark keywords _and_ bookmarklets). But I'm pretty surprised the functionality regressions were not tracked to start with and the apparent lack of explicit decision to ship with them apart from "well, its too late now"...