User Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release) Build ID: 20140703154127 Steps to reproduce: I'm trying to setup FF30 stable with Sync on a new PC. Already have FF31b with sync on old PC. 1. Click "Get started" 2. Click "Already have an account" Actual results: 1. navigates to about:accounts, Headline shows 'reate a FF account' ('C' is missing) 2a. Headline shows 'ign in' ('S' is missing) 2b. Cannot enter email as I only have an account name on old PC Expected results: a) UI should show missing characters b) login should be possible with account name, not email only
It sounds like you're using "old sync" instead of Firefox Accounts. I'm fairly sure we removed the ability to set up that type of sync in Firefox 29, even if syncing (when already set up) still works. C.f. https://support.mozilla.org/en-US/kb/how-to-update-to-the-new-firefox-sync?as=u&utm_source=inproduct#w_what-if-i-dont-want-to-update-to-the-new-sync The letters being missing sounds very strange. Can you post a screenshot?
Component: Untriaged → Sync
Summary: Sync sign-up confusing + broken → First letter of headers missing on about:accounts
Created attachment 8451650 [details] Screenshot (this one ff31b) Here we go
Thank you for the "old sync account" hint. That's solved. My confusion came from the fact that I was already on a current FF version and didn't understand why my account should be "old". The first letter problem is reproducible on two laptops of different brand.
We've seen this issue in IE 9, but never Firefox: https://github.com/mozilla/fxa-content-server/issues/1267 We'll investigate further.
I see the same at the nl version of https://accounts.firefox.com/signin
in firefox 31.0
Created attachment 8454869 [details] firefoxaccount.png the dutch version doesn't only mis the the first letter but also all the 'a'.... see screenshot
This is a broken web font issue. We've made some progress on this: https://github.com/mozilla/fxa-content-server/issues/1267 Fix should be out in week or so.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.