On Sun, Jan 12, 2014 at 6:41 AM, Lester Caine <[email protected]> wrote: > Hannes Magnusson wrote: >> >> Ahh. Got it. >> >> So there is nothing your skillset can do to fix the issue described in >> the bug report? >> That is a huge disappointment to me. >> >> Is there anything else you can contribute with? > > > HAS something been committed to php.net? > Currently php.net is not throwing an error, but it then bounces to the uk > mirrors - which are. There is no pop-up on IE7 from typeahead.js and there > is no 'skillset' that can provide it! Although typeahead.js does work on IE7 > if you remove the html5 bits and the html5.js 'fix', which is why I say that > creating a legacy style is an option to fix things. Drop the html5/bootstrap > style and things get easier. But I can't see where the reported fix to > typeahead.js fits into the local js versions.
Thats Ok. If you look at the bug report again you'll see Sherif Ramadan found the problem and is merging the fix. > What has to be decided is simply what level browser compatibility is > acceptable. Github has already dropped IE7 so any links through to there That was decided long time ago. We do not officially support IE. The reason for that is we don't have people running Windows in our team so we have no way of supporting it. However. When a bug report comes, we do our best to triage it and see if we can resolve it somehow. > from PHP hit a problem anyway. While adding html5.js has made other sub > domains usable on IE7, there is still a problem with rendering the > nav/footer elements which are being rendered correctly on php.net. Some > element of bootstrap fixes come into the equation here since the php.net > sections are using bootstrap styles while the other sub domains have > different styles. This may just be a css problem but at least on > wiki.php.net there is a problem with dokuwiki since that does not support > IE7 ... You are mixing subdomains with www. Please raise a different thread for each one if you'd like to discuss this problem further. Its not productive the way you are doing it now. We cannot follow your train of though, especially when you only do braindumps rather then clear replies. Under no circumstances shall anyone reply to a automated ticket update mail, like you did here originally, as most people filter these away into a dedicated "read later folder" and may "mark all as read" once in a while if they don't have the time to catch up on tickets - never ever seeing this discussion then. Throughout this discussion I have been trying to reach you and hoping for coherent replies to the specific issues, but that seems like will never happen - so now you will have to follow the rules of the game like everyone else, I cannot make further special cases for you. Thank you for your understanding. -Hannes -- PHP Webmaster List Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
