Forum:Mobile Issues: Difference between revisions
(9 intermediate revisions by 3 users not shown) | |||
Line 12: | Line 12: | ||
*Add notifications for users who receive new messages. | *Add notifications for users who receive new messages. | ||
*Navigation bars are missing. Those are important on pages such as [[Gear]]. | *Navigation bars are missing. Those are important on pages such as [[Gear]]. | ||
*Some articles with tables that don't work well; either the width is too wide or colours are missing. Is there a way to improve them? | *Some articles with tables that don't work well; either the width is too wide<s> or colours are missing</s>. Is there a way to improve them? | ||
**[[Command Matrix]] | **[[Command Matrix]] | ||
**[[Highwind ( | **[[Highwind (raft)]] | ||
**[[Game:Traverse Town#Treasures]] | **[[Game:Traverse Town#Treasures]] | ||
*Add a "collapse section" feature at the end of each section. This is so that people do not need to scroll back up long sections to reach the table of contents and search bar. | *Add a "collapse section" feature at the end of each section. This is so that people do not need to scroll back up long sections to reach the table of contents and search bar. | ||
*At the moment, suites are plain text. Is there any way of making them look better (e.g. adding a box around them)? | *At the moment, suites are plain text. Is there any way of making them look better (e.g. adding a box around them)? | ||
*Hover text does not function. {{User:TheFifteenthMember/Sig1}} 15:51, 31 August 2014 (UTC) | *Hover text does not function. {{User:TheFifteenthMember/Sig1}} 15:51, 31 August 2014 (UTC) | ||
*All collapsible boxes do not function. They are instead left blank. This is a huge problem as they are essential for [[Neverland#Settings and areas|area maps]] and [[Neverland#Enemies|enemy sections]] as well as individual articles, such as [[Theater Mode]]. I'm aware that collapsible boxes are impossible to work on mobiles but if this is an insurmountable problem, I feel it's something too major to give up on. {{User:TheFifteenthMember/Sig1}} 19:31, 12 September 2014 (UTC) | |||
===Resolved=== | ===Resolved=== | ||
Line 39: | Line 40: | ||
Our table of contents should behave exactly like the Wikipedia mobile site. On tablets it looks like [http://i.imgur.com/sG6KAQG.png this] and on phones everything is collapsed and the section headers serve as the TOC. Navigation bars being hidden is a design choice, also just like on Wikipedia, to keep the bottom of articles from being this huge thing of tables. They maybe shouldn't be used in the body of articles but it is possible to bring them back. What is an example of hover text? --[[User:Porplemontage|Porplemontage]] ([[User talk:Porplemontage|talk]]) 18:48, 31 August 2014 (UTC) | Our table of contents should behave exactly like the Wikipedia mobile site. On tablets it looks like [http://i.imgur.com/sG6KAQG.png this] and on phones everything is collapsed and the section headers serve as the TOC. Navigation bars being hidden is a design choice, also just like on Wikipedia, to keep the bottom of articles from being this huge thing of tables. They maybe shouldn't be used in the body of articles but it is possible to bring them back. What is an example of hover text? --[[User:Porplemontage|Porplemontage]] ([[User talk:Porplemontage|talk]]) 18:48, 31 August 2014 (UTC) | ||
:The problem with the section headers serving as the ToC is they don't show sub-sections and we tend to include a lot of sub-sections in our articles, making the need to jump to a specific one important. Could the phones have a collapsed ToC like the tablets, or something similar? Can navigation bars be collapsible in mobile viewing? If so, they shouldn't pose much of a hindrance when they're visible. [[KHWiki:Roundtable|The date in the first line of this page has a hover link]]. {{User:TheFifteenthMember/Sig1}} 19:30, 31 August 2014 (UTC) | :The problem with the section headers serving as the ToC is they don't show sub-sections and we tend to include a lot of sub-sections in our articles, making the need to jump to a specific one important. Could the phones have a collapsed ToC like the tablets, or something similar? Can navigation bars be collapsible in mobile viewing? If so, they shouldn't pose much of a hindrance when they're visible. [[KHWiki:Roundtable|The date in the first line of this page has a hover link]]. {{User:TheFifteenthMember/Sig1}} 19:30, 31 August 2014 (UTC) | ||
::I tried forcing the table of contents to display with CSS but that didn't work. I brought back nav templates and copied over the collapsible code, but they didn't collapse. Another annoying thing about the nav templates is that they are always hidden under the last section, whether it be External links, Trivia etc. and they don't really belong under those headings. I added the dotted underline to hover text but I think that was removed as a design choice too. The hover text already worked - you can test it on a desktop in mobile view. But touchscreen browsers may not implement that ability so since it doesn't work on those devices the text was made to look normal. --[[User:Porplemontage|Porplemontage]] ([[User talk:Porplemontage|talk]]) 22:06, 31 August 2014 (UTC) | |||
:::I guess we have to make do with the collapsed sections as a ToC, then. For the Gear page, we can rewrite a second "Gear" article specifically for mobile viewing, like how we're planning on creating a second main page for mobiles, so the navigation bar problem can be solved that way. Is it possible to modify the hover function so that tapping on the text activates hover links and tapping away goes back? Huge thanks for your efforts! {{User:TheFifteenthMember/Sig1}} 22:26, 31 August 2014 (UTC) | |||
::::For the Gear page you should just include the links without the nav templates and then it will work for both. And then desktop users won't have to click "show" on everything. Or [http://www.khwiki.com/index.php?title=Template%3ASkillGear&diff=639233&oldid=618555 here] [http://www.khwiki.com/index.php?title=Gear&diff=639234&oldid=631717 is] one way to fix it. Right now hover is just title text, which isn't supported by mobile browsers. It would be tricky - probably have to look into a JavaScript solution and one that actually works with mobile. I've removed the hover underlining again since tapping doesn't work and that's misleading for mobile users. --[[User:Porplemontage|Porplemontage]] ([[User talk:Porplemontage|talk]]) 22:58, 31 August 2014 (UTC) | |||
Thanks again! We scarcely use hover links anyway so it's not a huge issue if you can't get it to work. {{User:TheFifteenthMember/Sig1}} 23:05, 31 August 2014 (UTC) | |||
I agree that the collapsible boxes do need some fix. However, I wouldn't expect one, as it seems that the problem is a software limitation. I just checked Wikipedia's mobile site, and it doesn't display collapsible nav boxes or such. I'd imagine that there'd be a fix sometime soon. In the meantime, I don't think there's much we can do about it except wait for the next release of MediaWiki or something. {{KeybladeSpyMaster/Sig}} 19:49, 12 September 2014 (UTC) | |||
:In that case, on the mobile's main page, we should have a notice saying something along the lines of "Welcome to the KHWiki's mobile port, intended for light viewing. To browse the Wiki in its entirety with all features enabled, visit the desktop site<small>(link to desktop version)</small>". Then, readers will see the mobile site as an option, rather than the preferred method of browsing, and will understand that the mobile site has limitations. {{User:TheFifteenthMember/Sig1}} 19:55, 12 September 2014 (UTC) | |||
:It was a design choice that the extension not be compatible with collapsible elements, so I wouldn't expect a fix for it. See [https://bugzilla.wikimedia.org/show_bug.cgi?id=53136 this bug report]. --[[User:Porplemontage|Porplemontage]] ([[User talk:Porplemontage|talk]]) 20:16, 12 September 2014 (UTC) |
Latest revision as of 20:16, 12 September 2014
|
Issues[edit]
Unresolved[edit]
Submit your issues here!
- There is no easily accessible Table of Contents. TheFifteenthMember 01:24, 27 July 2014 (UTC)
- In the Roundtable, we agreed that we wanted to see a Table of Contents similar to wikipedia's.
- Add notifications for users who receive new messages.
- Navigation bars are missing. Those are important on pages such as Gear.
- Some articles with tables that don't work well; either the width is too wide
or colours are missing. Is there a way to improve them? - Add a "collapse section" feature at the end of each section. This is so that people do not need to scroll back up long sections to reach the table of contents and search bar.
- At the moment, suites are plain text. Is there any way of making them look better (e.g. adding a box around them)?
- Hover text does not function. TheFifteenthMember 15:51, 31 August 2014 (UTC)
- All collapsible boxes do not function. They are instead left blank. This is a huge problem as they are essential for area maps and enemy sections as well as individual articles, such as Theater Mode. I'm aware that collapsible boxes are impossible to work on mobiles but if this is an insurmountable problem, I feel it's something too major to give up on. TheFifteenthMember 19:31, 12 September 2014 (UTC)
Resolved[edit]
- Talk bubbles are completely broken. TheFifteenthMember 00:10, 20 July 2014 (UTC)
- Mobile's main page is much less effective due to its incredible length. Is there any possibility of creating an alternate main page to be displayed on mobiles? TheFifteenthMember 00:10, 20 July 2014 (UTC)
- Some tables can't be viewed in its entirety, requiring tedious scrolling left-and-right in order to read them. Is this a non-solvable problem, dependant on the mobile's screen width? TheFifteenthMember 00:10, 20 July 2014 (UTC)
- Recent Changes is not on the mobile sidebar. TheFifteenthMember 12:40, 21 July 2014 (UTC)
- KHWiki:Traverse Town pages are broken. TheFifteenthMember 12:41, 21 July 2014 (UTC)
Comments[edit]
OK, talk bubbles and infoboxes are better now. If there are other table issues, please provide examples. A separate mobile main page is possible. The way elements are selected to appear on the mobile main page is with a div of id="mf-???"
where ???
can be anything (also, adding a div title
parameter creates a heading). What I've done is select elements from the existing main page to appear on mobile. To create a separate mobile main page from scratch, all you you have to do is use a single <div id="mf-main" style="display:none;">...</div>
containing the mobile main page at the bottom of the main page, and it will be hidden from view. Then make it show up only for mobile users using MediaWiki:Mobile.css. --Porplemontage (talk) 02:17, 20 July 2014 (UTC)
I added Recent Changes to the sidebar. Traverse Town is just too wide? --Porplemontage (talk) 22:00, 21 July 2014 (UTC)
On a phone the sections should be collapsed by default and the collapsed section titles serve as the Table of Contents. On a tablet or desktop in mobile mode the sections are expanded by default and a Table of Contents should show up. --Porplemontage (talk) 17:25, 27 July 2014 (UTC)
- Yes, Traverse Town is too wide. As I've posted above, we would like a Table of Contents similar to Wikipedia's setup. TheFifteenthMember 15:54, 31 August 2014 (UTC)
- Regarding the Table of Contents, I noted in the Roundtable that the TOC desired doesn't appear in the Wikipedia Mobile Site, but rather, their app (the screenshot appears to be the iOS app). I don't know if a TOC is possible on the site like theirs. This is the TOC that the Wikipedia site uses (click!)KeybladeSpyMaster 16:05, 31 August 2014 (UTC)
Our table of contents should behave exactly like the Wikipedia mobile site. On tablets it looks like this and on phones everything is collapsed and the section headers serve as the TOC. Navigation bars being hidden is a design choice, also just like on Wikipedia, to keep the bottom of articles from being this huge thing of tables. They maybe shouldn't be used in the body of articles but it is possible to bring them back. What is an example of hover text? --Porplemontage (talk) 18:48, 31 August 2014 (UTC)
- The problem with the section headers serving as the ToC is they don't show sub-sections and we tend to include a lot of sub-sections in our articles, making the need to jump to a specific one important. Could the phones have a collapsed ToC like the tablets, or something similar? Can navigation bars be collapsible in mobile viewing? If so, they shouldn't pose much of a hindrance when they're visible. The date in the first line of this page has a hover link. TheFifteenthMember 19:30, 31 August 2014 (UTC)
- I tried forcing the table of contents to display with CSS but that didn't work. I brought back nav templates and copied over the collapsible code, but they didn't collapse. Another annoying thing about the nav templates is that they are always hidden under the last section, whether it be External links, Trivia etc. and they don't really belong under those headings. I added the dotted underline to hover text but I think that was removed as a design choice too. The hover text already worked - you can test it on a desktop in mobile view. But touchscreen browsers may not implement that ability so since it doesn't work on those devices the text was made to look normal. --Porplemontage (talk) 22:06, 31 August 2014 (UTC)
- I guess we have to make do with the collapsed sections as a ToC, then. For the Gear page, we can rewrite a second "Gear" article specifically for mobile viewing, like how we're planning on creating a second main page for mobiles, so the navigation bar problem can be solved that way. Is it possible to modify the hover function so that tapping on the text activates hover links and tapping away goes back? Huge thanks for your efforts! TheFifteenthMember 22:26, 31 August 2014 (UTC)
- I tried forcing the table of contents to display with CSS but that didn't work. I brought back nav templates and copied over the collapsible code, but they didn't collapse. Another annoying thing about the nav templates is that they are always hidden under the last section, whether it be External links, Trivia etc. and they don't really belong under those headings. I added the dotted underline to hover text but I think that was removed as a design choice too. The hover text already worked - you can test it on a desktop in mobile view. But touchscreen browsers may not implement that ability so since it doesn't work on those devices the text was made to look normal. --Porplemontage (talk) 22:06, 31 August 2014 (UTC)
- For the Gear page you should just include the links without the nav templates and then it will work for both. And then desktop users won't have to click "show" on everything. Or here is one way to fix it. Right now hover is just title text, which isn't supported by mobile browsers. It would be tricky - probably have to look into a JavaScript solution and one that actually works with mobile. I've removed the hover underlining again since tapping doesn't work and that's misleading for mobile users. --Porplemontage (talk) 22:58, 31 August 2014 (UTC)
Thanks again! We scarcely use hover links anyway so it's not a huge issue if you can't get it to work. TheFifteenthMember 23:05, 31 August 2014 (UTC)
I agree that the collapsible boxes do need some fix. However, I wouldn't expect one, as it seems that the problem is a software limitation. I just checked Wikipedia's mobile site, and it doesn't display collapsible nav boxes or such. I'd imagine that there'd be a fix sometime soon. In the meantime, I don't think there's much we can do about it except wait for the next release of MediaWiki or something. KeybladeSpyMaster 19:49, 12 September 2014 (UTC)
- In that case, on the mobile's main page, we should have a notice saying something along the lines of "Welcome to the KHWiki's mobile port, intended for light viewing. To browse the Wiki in its entirety with all features enabled, visit the desktop site(link to desktop version)". Then, readers will see the mobile site as an option, rather than the preferred method of browsing, and will understand that the mobile site has limitations. TheFifteenthMember 19:55, 12 September 2014 (UTC)
- It was a design choice that the extension not be compatible with collapsible elements, so I wouldn't expect a fix for it. See this bug report. --Porplemontage (talk) 20:16, 12 September 2014 (UTC)