Refactor all links from a form like http://www.creat..
to //www.creat… I don't know if that notation is backward compatible with most browsers though. -- Kennisland | www.kennisland.nl | t +31205756720 | m +31643053919 | @mzeinstra On Jun 24, 2013, at 17:57 , Jonas Öberg <[email protected]> wrote: > Hi Maarten, > > I don't see why this shouldn't be protocol relative. > What is needed to be done to revise this? > > Sincerely, > Jonas > > > On Mon, Jun 24, 2013 at 5:54 PM, Maarten Zeinstra <[email protected]> wrote: > Hi all, > > I use the HTTPS everywhere plugin for Chrome and that messes up some of the > CreativeCommons.org pages. Chrome doesn't allow loading .js and .css files > from HTTP links within HTTPS pages anymore. This severely messes up pages > like all legalcode pages and the namespace page. > > I already discussed this with Nathan Kinkade, but he indicated that he will > not have time to work on it and it seems to be something that is possibly > only the case in the newest Chrome browser a problem. Chrome doesn't seem to > try to resolve those links in https. > > However I think that more browser will follow Chrome's lead in this and that > we should (re)work these pages to either be protocol relative or force https. > > Would we agree? > > Cheers, > > Maarten > > > -- > Kennisland | www.kennisland.nl | t +31205756720 | m +31643053919 | @mzeinstra > > > > > > _______________________________________________ > cc-devel mailing list > [email protected] > http://lists.ibiblio.org/mailman/listinfo/cc-devel > >
_______________________________________________ cc-devel mailing list [email protected] http://lists.ibiblio.org/mailman/listinfo/cc-devel
