This is a re-post from Chromium tracker, I was asked to port it here as they believe it's an upstream bug. Chrome Version: 11.0.696.77 OS Version: Windows 7, Ubuntu Linux, Debian Linux Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Safari 5: Failed Firefox 4.x: Passed IE 9: Passed Safari test was done with Adobe Browserlab. What steps will reproduce the problem? 1. Create a base64 data stream of your font and use in @font-face. 2. Use proper punctuation spacing. EXP: [, data] and not [,data] What is the expected result? Woff font to show up as embedded. What happens instead? I thought I was stupid until I figured it out. Examples: Works: @font-face { font-family: museo; src: url('data:application/x-woff;base64,data-here') format('woff'); } Fails: @font-face { font-family: museo; src: url('data: application/x-woff; base64, data-here') format('woff'); }
Could you please provide a test reduction with the appropriate data?
This doesn’t appear to be in any way specific to WOFF or even to CSS. It appears as if "; base64" is parsed differently from ";base64" by the loading code.