Hannes Magnusson wrote:
What is this javascript you speak of that is missing on the subdomains?
The move to html5/css3 means that many of the older browsers simply can't
display new content.
As has already been noted, if javascript is disabled at the client, then all we
can really do is tell them that pages can't be displayed, so there should
probably be a proper management of that state?
Under the hood there are a couple of elements that are used to support different
aspects of html5, and html5shiv.js provides the basic styling elements to IE6, 7
and 8.
https://github.com/aFarkas/html5shiv
The next element is modernizer http://modernizr.com/docs/ which if you look at
the download page includes html5shiv but normally you would select just the
elements you need. It depends on the style model just what sections need to be
added, and adding everything is a little overkill.
Bootstrap2 used to provide a transparent path to support these older browsers,
but Bootstrap3 dropped support for a number of the older ones, in particular
IE7. It also changed the style model drastically, but I think while the main
site seems to be using BS2 styles? The sub-domains are not? But BS2 is now
deprecated and things like 'row-fluid' have been superseded, so the main site is
already obsolete! Now that html5shiv.js is loading we get a fixed width vertical
stack for all of the domains including php.net, but I don't think it can be
fixed simply by adding the extra modernizer.js or additional bootstrap or any
other code. The layout needed to be designed correctly first :(
I'm using ink http://ink.sapo.pt/getting_started which with a little care to the
layout model is usable on even IE6, but IE7 does not support 'responsive'
layout, defaulting back to a fixed one, but one without the 'vertical stack'
problem.
At this stage I think we have to cut losses and simply add warning to IE7 users
in the same way as 'non-javascript' users, and direct them to switch browsers.
Forgive me for being young and stupid, but why do you need to import
the full content of the wiki into a database?
Is a page or two not enough? - There is bundled page listing all the
styles it uses: https://wiki.php.net/wiki:syntax
Google search is useless across php.net and it's sub domains. In order to search
of content relating to particular aspects of PHP that have been changed between
versions I am almost having to manually search through individual pages so I
want a proper searchable set of content which I can properly filter initially
simply by language, but also by content type.
http://phpsurgery.org/search/ will give you the idea, and things like news items
will be managed as news articles, comments added to manual entries as
'comments'. and so on. I have most news group messages since 1999 already
available as a local searchable archive, and this will just add to that ...
phpsurgery has the same sort of javascript problem on IE7 which is why I said
ink even 'ink' is not a solution to the problem :( If I move all the scripts to
the head section, then the error goes away ...
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
--
PHP Webmaster List Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
