FreeBSD users are being shown Windows content instead of Linux
Categories
(support.mozilla.org :: Knowledge Base Software, task, P4)
Tracking
(Not tracked)
People
(Reporter: grahamperrin, Unassigned)
References
()
Details
Attachments
(2 files)
Firefox and Firefox Quantum have a standard shortcut:
Ctrl+Shift+O
Show All Bookmarks
– not documented at:
Keyboard shortcuts - Perform common Firefox tasks quickly | Firefox Help
https://support.mozilla.org/kb/keyboard-shortcuts-perform-firefox-tasks-quickly
For search purposes (discoverability of this bug), also:
- Control-Shift-O
- Ctrl + Shift + O (a style of writing currently used at the URL above and at other Mozilla pages such as https://developer.mozilla.org/docs/Tools/Keyboard_shortcuts)
- Ctrl+⇧ Shift+O (a style of writing currently used at https://wikipedia.org/wiki/Table_of_keyboard_shortcuts)
Reporter | ||
Comment 1•6 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1328637#c21 offers clarification.
I should treat this bug as a Tier-2 Knowledge Base content issue; misleading content (for Firefox 64 on Windows 8) is presented, by default, to Firefox 65.0 on FreeBSD-CURRENT.
I stumbled across the hidden option to customise content only after using the Editing Tools menu to view (not edit) history.
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Comment 2•6 years ago
|
||
Sorry, Tier-3. I forgot, FreeBSD is Tier-3.
Reporter | ||
Updated•6 years ago
|
Comment 3•6 years ago
|
||
It's listed as "Library window (Bookmarks) ".
Do you think we should change it from "Library window (Bookmarks) " to "Show All Bookmarks"?
Comment 4•6 years ago
|
||
(In reply to Chris Ilias [:cilias] from comment #3)
Created attachment 9043319 [details]
Screenshot_2019-02-12 Keyboard shortcuts - Perform common Firefox tasks quickly Firefox Help.pngIt's listed as "Library window (Bookmarks) ".
Do you think we should change it from "Library window (Bookmarks) " to "Show All Bookmarks"?
I think the problem is that FreeBSD users get the Windows content instead of the Linux content.
Reporter | ||
Comment 5•6 years ago
|
||
(In reply to :Gijs (he/him) from comment #4)
I think the problem is that FreeBSD users get the Windows content instead of the Linux content.
I think so.
The broader problem – for any SUMO content that might be automatically, wrongly customised (think beyond Firefox or FreeBSD; think of readers using any browser, anywhere; of the Wayback Machine, and so on) – is ambiguity. We have no hint of customisation, no hint of incompleteness.
An average reader, not intending to edit a knowledge base, would not think to use an editing menu to discover the incompleteness of a document. Not good UX.
Compare with e.g. https://developer.mozilla.org/docs/Tools/Keyboard_shortcuts, which is clear, non-ambiguous. A good overview.
Comment 6•6 years ago
|
||
OK, there are two issues:
- FreeBSD users get the Windows content
- The discoverability of the OS-Picker
I've updated the summary/component of this bug for the first issue.
The second issue is bug 1095476.
Reporter | ||
Comment 7•6 years ago
|
||
FreeBSD users get the Windows content
Also content for the wrong version of Firefox. Customised for 64 when browsed with 65. Should I raise a separate bug?
Comment 8•6 years ago
|
||
(In reply to Graham Perrin from comment #7)
FreeBSD users get the Windows content
Also content for the wrong version of Firefox. Customised for 64 when browsed with 65. Should I raise a separate bug?
This might be why you are seeing content for Firefox 64:
Firefox 64 is still the default version for SUMO articles viewed in other browsers, even though Firefox 65 is the latest version. I confirmed this by viewing https://support.mozilla.org/en-US/kb/extension-recommendations in Google Chrome. Screenshot: https://support.mozilla.org/en-US/gallery/image/33400
Roland or another admin will need to change the default Firefox version to Firefox 65. Related discussion:
https://support.mozilla.org/en-US/forums/knowledge-base-articles/712759#post-75491 [Attn: Admin] Version picker updates needed
Comment 10•6 years ago
|
||
Updated•6 years ago
|
Comment 11•6 years ago
|
||
The fix for this bug is live in production. FreeBSD users should now get Linux content.
Description
•