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

Re: Upcoming code re-deployment

From: PhistucK <phistuck@gmail.com>
Date: Sat, 6 Sep 2014 00:28:32 +0300
Message-ID: <CABc02_+7Apo7VmmafZvOyfVA921Po4YDVUQhgOr69XpyprU2=Q@mail.gmail.com>
To: Renoir Boulanger <renoir@w3.org>
Cc: "public-webplatform@w3.org" <public-webplatform@w3.org>
Note that WOFF files already have CORS headers (I checked it before sending
the previous e-mail), only SVG files did not have them.

I submitted a pull request. Do you think there might have been a good
reason they were put as the first choice instead of a fallback choice?
Perhaps ugly Windows XP rendering when using Chrome (this has been the main
reason for using SVG fonts so far)? Do you support this change nevertheless?




☆*PhistucK*


On Sat, Sep 6, 2014 at 12:15 AM, Renoir Boulanger <renoir@w3.org> wrote:

> That’s a nice finding PhistucK!
>
> I just fixed it.
>
> If you can help with refactoring the CSS call, that would be great! Take
> a look at the repositories I mention below.
>
>
> # About the CORS header and the SVN Files:
>
> The web servers *are* sending the CORS headers for the fonts, but Fastly
> strips them out —I haven’t realized that.
>
> I worked a way to enable them [0] only for SVG files through Fastly.
> I’ll take a look later for improving our Fastly configs.
>
> If you want to see source, not everything is available on GitHub, but I
> can give you access to our own installation of Gerrit [2].
>
>
> # Repositories you might want to see
>
> * Varnish/Fastly configuration [1]
> * The Skin AND extensions tweaks we are using [3]
> * The CSS you want to take a look at [4][5]
>
>
>   [0]: http://docs.fastly.com/guides/22958677/28491283
>   [1]: https://github.com/webplatform/varnish-configs
>   [2]: https://source.webplatform.org/r/#/
>   [3]: https://github.com/webplatform/mediawiki
>   [4]:
> https://github.com/webplatform/mediawiki/blob/master/skin/screen.css
>   [5]:
> https://github.com/webplatform/mediawiki/blob/master/skin/screen-edit.css
>
> Thanks for your help!
>
> Renoir
> ~
>
>
> On 2014-09-05, 2:29 PM, PhistucK wrote:
> > 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
> >>
> >>
> >
>
> --
> Regards,
>
> Renoir Boulanger  |  Developer operations engineer
> W3C  |  Web Platform Project
>
> http://w3.org/people/#renoirbhttps://renoirboulanger.com/  ✪
> @renoirb
> ~
>
Received on Friday, 5 September 2014 21:29:39 UTC

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