Closed
Bug 651226
Opened 13 years ago
Closed 12 years ago
Add 'winxp', 'win7' and 'win8' to showfor
Categories
(support.mozilla.org :: Knowledge Base Software, task, P1)
support.mozilla.org
Knowledge Base Software
Tracking
(Not tracked)
VERIFIED
FIXED
2012Q4
People
(Reporter: jsocol, Assigned: mythmon)
References
Details
(Whiteboard: u=user c=wiki p=3 s=2012.20)
Add 'winxp' and 'win7' operating systems to showfor. The current 'win' OS will continue to apply to all Windows versions; 'winxp' will apply to Windows XP; and 'win7' will apply to Windows Vista and 7. (Random thought: maybe it makes sense to start including the relevant JS identifying regex in the Python where we define the available OSes?)
Updated•13 years ago
|
Assignee: nobody → erik
Updated•13 years ago
|
Target Milestone: 2011Q2 → 2011Q3
Reporter | ||
Comment 1•13 years ago
|
||
Michael: Is this still something we need?
Target Milestone: 2011Q3 → ---
Comment 2•13 years ago
|
||
Hey, I just added platform-specific videos demonstrating how to show the bookmarks toolbar for Firefox on Windows 7 and OS X: https://support.mozilla.com/en-US/kb/Bookmarks%20Toolbar/compare?locale=en-US&to=19179&from=18660 These videos were made by Richard Milewski, and he's got a corresponding one for Windows XP: http://videos-cdn.mozilla.net/serv/labs/hackasaurus/ToolBar-XP-FF7.webm However, I guess we can't show this until this bug is fixed. No rush or anything, but just figured I'd mention it here. :)
Updated•12 years ago
|
Summary: Add 'winxp' and 'win7' to showfor → Add 'winxp', 'win7' and 'win8' to showfor
Updated•12 years ago
|
Assignee: erik → nobody
Comment 4•12 years ago
|
||
Taking this out of Erik's queue. I don't know the kb stuff very well, so I don't understand why this has been hanging around for a year now. Is this something that we need in the kb? Any idea why we were waiting to implement it?
Comment 5•12 years ago
|
||
(In reply to Will Kahn-Greene [:willkg] from comment #4) > Taking this out of Erik's queue. > > I don't know the kb stuff very well, so I don't understand why this has been > hanging around for a year now. Is this something that we need in the kb? Any > idea why we were waiting to implement it? actually windows 8 not release officially yet, but consumer preview works very stable here, so if we start editing kb for windows 8, it will be very helpful
Comment 6•12 years ago
|
||
Let's wait on this for the moment. This needs some thought and discussion.
Comment 7•12 years ago
|
||
As discussed in last week's KB meeting https://etherpad.mozilla.org/kb-2012-09-20 , we should finally add these to Kitsune. Here are my suggestions for UI and markup: UI: Windows XP Windows Vista/7 Windows 8 Markup: {for winxp} = Windows XP {for win7} = Windows Vista/7 {for win8} = Windows 8 Like James suggests in the description we should use the current {for win} to apply to all windows versions so that our current articles won't break and we can XP or 8 instructions as time allows.
Updated•12 years ago
|
Whiteboard: u=user c=wiki p=
Target Milestone: --- → 2012Q4
Comment 8•12 years ago
|
||
(In reply to Verdi [:verdi] from comment #7) Actually in the UI we probably want to list the Windows 7 & Vista choice as "Windows 7/Vista" instead of "Windows Vista/7" as I said in comment 7.
Comment 9•12 years ago
|
||
I'm adding this to the current sprint, assuming that this it's close to a one liner. Let's reevaluate if that is not the case.
Comment 10•12 years ago
|
||
This is more complicated than a 1pter as we don't currently do any OS version handling in showfor. And there is special logic that needs to be defined and implemented (I don't really know what "use the current {for win} to apply to all windows versions" exactly means). Let's try to define it: If I have this in my wiki syntax: {for win}Windows{/for} {for winxp}Windows XP{/for} {for win7}Windows 7/Vista{/for} {for win8}Windows 8{/for} What shows up in each of the following cases: 1- User selects Windows 2- User selects Windows XP 3- User selects Windows 7/Vista 4- User selects Windows 8 This is more like a 3pter as we the showfor js code is can be fragile. We'll need to add a bunch of unit tests for the new behavior.
Whiteboard: u=user c=wiki p= → u=user c=wiki p=3
Comment 11•12 years ago
|
||
Kadir: Does comment #10 mean this needs to get bumped out of the 2012.19 sprint? I think it does given what you said in comment #9.
Comment 12•12 years ago
|
||
Ricky, answering your question. In code: 1. {for win}Horse{/for} 2. {for winxp}Horse{/for} 3. {for win7}Horse/Vista{/for} 4. {for win8}Horse{/for} What we display: a- User has WindowsXP as OS 1a {for win}Horse{/for}= Horse 2a {for winxp}Horse{/for}= Horse 3a {for win7}Horse/Vista{/for}= NULL 4a {for win8}Horse{/for}= NULL b- User has Windows Vita or 7 as OS 1b {for win}Horse{/for}= Horse 2b {for winxp}Horse{/for}= NULL 3b {for win7}Horse/Vista{/for}= Horse 4b {for win8}Horse{/for}= NULL c- User has Windows 8 as OS 1c {for win}Horse{/for}= Horse 2c {for winxp}Horse{/for}= NULL 3c {for win7}Horse/Vista{/for}= NULL 4c {for win8}Horse{/for}= Horse
Updated•12 years ago
|
Whiteboard: u=user c=wiki p=3 → u=user c=wiki p=3 s=2012.20
Comment 13•12 years ago
|
||
I just moved this out of the 19th sprint, since this is way beyond a 1pointer that I first expected. Let's see if we can further break this down, or otherwise address this bug in the next sprint.
Comment 14•12 years ago
|
||
Note that {for win} is an option for markup but we users will only be able to choose winxp, win7 or win8 from the dropdown.
Updated•12 years ago
|
Priority: -- → P1
Comment 15•12 years ago
|
||
I haven't told him yet, but :mythmon will be learning about our showfor code in order to increase our bus factor to 2.
Assignee: nobody → mcooper
Comment 16•12 years ago
|
||
This article might help with how showfor is supposed to work: https://support.mozilla.org/en-US/kb/how-to-use-for
Assignee | ||
Comment 17•12 years ago
|
||
PR https://github.com/mozilla/kitsune/pull/911
Assignee | ||
Comment 18•12 years ago
|
||
Landed in https://github.com/mozilla/kitsune/commit/36d7e3fcd515d8cdfefa58d3c8eb163f24b9004b. Pushing to stage, but this isn't going to production until we get some more eyes on it.
Comment 19•12 years ago
|
||
I just deployed to prod.
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•