Created an attachment (id=1099192) overlapping DEFECT DESCRIPTION: The words is overlapping. REPRODUCING PROCEDURES: 1.Enter Setup Wizard via different way. 2.Go to the About Firefox OS screen. 3.Click "About Firefox OS"->Click "Your Privacy"->Click "Learn more" 4.Enter www.mozilla.org/telemetry/ ,you will find the words are overlapping.->KO EXPECTED BEHAVIOUR: The words should display normally. TEL:61400 ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: REPRODUCING RATE: For FT PR, Please list reference mobile's behavior:
I can repro this bug on Woodduck v2.0 and Flame v2.0. See attachments: verify_v2.0m.MP4 and logcat_v2.0m_0230.txt Reproduce rate: 5/5 Repro STR: 1.Enter FTU and connect a wifi. 2.Go to the "About Firefox OS" page. 3.Click "Learn more". 4.Enter "www.mozilla.org/telemetry/" ,you will find the words are overlapping.->KO. Note:There is no "Learn more" and "www.mozilla.org/telemetry/" icon in FTU on Flame 2.1&2.2. Woodduck 2.0 build: Gaia-Rev ddb406ebdb34ca6717eda14297dea98f26f1f412 Gecko-Rev 20943fe7b54c63a375952fbd8dd396a22ee893e7 Build-ID 20150114050313 Version 32.0 Device-Name jrdhz72_w_ff FW-Release 4.4.2 FW-Incremental 1421183152 FW-Date Wed Jan 14 05:06:17 CST 2015 Flame 2.0 build: Gaia-Rev 31d6c9422cd0a8213df9f96019c9ab7168ec3ab3 Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/f2b6017e84eb Build-ID 20150113160201 Version 32.0 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20150113.192825 FW-Date Tue Jan 13 19:28:37 EST 2015 Bootloader L1TC000118D0 Flame 2.1 build: Gaia-Rev 6957ac8a322234ec99c8abb7cc18dc6a2e0176db Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/6600eba54256 Build-ID 20150113161204 Version 34.0 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20150113.192836 FW-Date Tue Jan 13 19:28:47 EST 2015 Bootloader L1TC000118D0 Flame 2.2 build: Gaia-Rev 7c5b27cad370db377b18a742d3f3fdb0070e899f Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/748b20315f75 Build-ID 20150113162504 Version 37.0a2 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20150113.194114 FW-Date Tue Jan 13 19:41:25 EST 2015 Bootloader L1TC000118D0
Hi Sam, Could you help to check this issue? It seems to be special case with FTU browser. Thanks!
Hrm, I've definitely seen this before, I wonder if we're requesting the wrong url or something. Ferndando, can you remember how we resolved this, or find the bug (I'm about to sign off for the day)
We load the external url localised using the file 'external_links.js', I checked and we load it correctly (https://wiki.mozilla.org/telemetry, that redirects to https://wiki.mozilla.org/Telemetry/FAQ). It's the webpage rendering with errors for lower resolutions, maybe a CSS media-query going wrong? Same happening on browser (Firefox and Chrome), attached images
Moving to websites / wiki component
This is an upstream issue in the Vector Mediawiki skin, as I'm seeing the same behavior on en.wikipedia.org in Firefox and Chrome desktop versions when I make the view port very narrow. The MozillaWiki team is planning to implement the MobileFrontend extension (bug 1051189) in order to provide a better experience for mobile users. That work is next on our roadmap, but we have limited resources so I can't say specifically when it will be available.
Thanks Christie. Moving back to FxOS / FTE component so we can track this. The content is legible, but its not a good experience. Also note this URL is the same we show to existing (1.* and 2.0) phones (https://wiki.mozilla.org/telemetry redirects to https://wiki.mozilla.org/Telemetry/FAQ) so this affects phones in the market today.
Peter, next steps? There is a fix in the pipeline for this but its targeted for this quarter. We could stand up the content outside the wiki but getting it localized (again) might take time?
I'm not too concerned about blocking the release or anything on this. Let's just wait for a fix on the wiki.
(In reply to Peter Dolanjski [:pdol] from comment #14) > I'm not too concerned about blocking the release or anything on this. Let's > just wait for a fix on the wiki. Ok, moving back to wiki component in that case so its on their radar to check when 1051189 lands.