W3C home > Mailing lists > Public > public-webplatform@w3.org > September 2014

Re: Upcoming code re-deployment

From: PhistucK <phistuck@gmail.com>
Date: Fri, 5 Sep 2014 21:29:42 +0300
Message-ID: <CABc02_JnqNKc5bWEVfQiLN411FDwT8FsVdGu7XSXLWGHbUV6Cg@mail.gmail.com>
To: Renoir Boulanger <renoir@w3.org>
Cc: List WebPlatform public <public-webplatform@w3.org>
Thank you!

Your announcement made me look at the Developer Tools (moving the font to a
different origin) and these are my findings -
1. The wpSymbols SVG font does not have CORS headers, so it will stop
working in Chrome 37
<https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/sU138vJ_PI0>
and later and may introduce some latency (Chrome might load the SVG font,
see that it does not have CORS headers, reject it and try the next one. The
worst case scenario is that it will not try the next one, but I am not sure
this is the logic it employs).
2. Why is the SVG version placed first in the @font-face declaration? Only
WebKit based browsers support it. Also, I know that Chrome is considering
dropping support for SVG fonts
<https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/pYbbUcYvlYY>
altogether (Chrome 38 only supports SVG fonts on Windows XP and Windows
Vista), so I would move away from them (or at least move them below the
WOFF version) as soon as possible and perhaps only list it as a fallback,
for older WebKit based browsers that do not support WOFF
<http://caniuse.com/#feat=woff>.

If you can point me to the open source repository for the relevant CSS, I
can submit a pull request for the CSS part (moving the SVG variant below
the WOFF variant), of course.
I assume that the CORS headers issue is probably a configuration toggle
that does not exist in the open source repository.


☆*PhistucK*


On Fri, Sep 5, 2014 at 8:35 PM, Renoir Boulanger <renoir@w3.org> wrote:

> Hi all,
>
> (re)Deployment is finished; everything went well.
>
> Renoir
> ~
>
> On 2014-09-05, 11:33 AM, Renoir Boulanger wrote:
> > Hi All,
> >
> > In the afternoon (about 13:00 EST), I will be rolling out a code sync
> > job that will last about a few minutes and nothing should be visible.
> >
> > It will be a re-deployment of the currently running software.
> >
> > The reason we are advising is that syncing files across servers will
> > take longer than a few seconds.
> >
> > Along with the new push, we are changing the location of various files
> > assets such as fonts and icons over to www.webplatform.org.
> >
> > This is one of the a series of steps in order to speed up page load time
> > and allow us to serve the site over both HTTP and HTTPS.
> >
> > To see the GitHub modules in question, head over to the status post [0].
> >
> >   [0]: http://status.webplatform.org/post/96705823105
>
>
Received on Friday, 5 September 2014 18:30:49 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:21:03 UTC