Bug #66371 [Asn]: JavaScript (I think) causing error on all pages

Edit report at https://bugs.php.net/bug.php?id=66371&edit=1 ID: 66371 User updated by: TygerGilbert at USAWebAdv dot com Reported by: TygerGilbert at USAWebAdv dot com Summary: JavaScript (I think) causing error on all pages Status: Assigned Type: Bug Package: Website problem Operating System: WinXP w/IE-8 PHP Version: Irrelevant Assigned To: googleguy Block user comment: N Private report: N New Comment: Yea! Thank you GoogleGuy and Bjori! I will wait with baited breath (breath that smells like fish bait) to see the results of your great work! Previous Comments: ------------------------------------------------------------------------ [2014-01-12 05:48:10] bjori@php.net Patch it please. ------------------------------------------------------------------------ [2014-01-12 03:28:01] googleguy@php.net It appears the problem exists in typehead.js and only effects IE8 users, as far as I can tell. I managed to track down the patch from twitter/typehead here https://github.com/twitter/typeahead.js/pull/457/files which details the issue found in PR 457 here https://github.com/twitter/typeahead.js/pull/457 Currently this PR has only been merged, but no release was made since 0.9.3, so we can either patch it manually or wait for the next release to update typehead.js It's a simple fix anyway. ------------------------------------------------------------------------ [2014-01-09 07:29:53] TygerGilbert at USAWebAdv dot com cmbecker69@, IMHO it doesn't matter what browser a developer uses to browse the web. It's the users who matter for ANY website, and since there is still a large number of users who still prefer IE-8, a site shouldn't break for them. I think it's called "backward compatibility." I understand that most users of the PHP.net site are developers, but if anything, I think that would make it even more important that PHP.net be the model of compatibility and ease of use in its entirety, particularly since there is no alternative site available. Letting the site behave badly for some older browsers just isn't a good example to set. Maybe I'm too sensitive to the idea of abandoning them because I'm an "old browser" myself at 65 now, but I'm still capable of providing an insight into the attitudes of a that large body of WinXP/IE-8 users who just won't go away yet. That insight can be carried over into a lot of other websites for the developer who is wise enough to listen. Fancy JavaSc! ript functions and exotic page behavior can often be more of detriment to easy use than a benefit. ------------------------------------------------------------------------ [2014-01-09 01:16:52] bjori@php.net Someone mentioned typeahead.js being a problem somewhere else too.. Maybe that plugin just doesn't like IE8? Adam.. Could you check it out? ------------------------------------------------------------------------ [2014-01-09 01:05:43] cmbecker69 at gmx dot de I can confirm the issues regarding IE 8. After stopping the script, the error console reports "Process aborted in typeahead.min.js line 7 character XYZ", where XYZ has different values (e.g. 298, 633, 6762). This happens apperently independent of whether I try to continue script execution several times or not. Especially character 633, which is inside the header of a for loop, is reported quite often. Unfortunately, it doesn't seem to be possible to debug minified JavaScript files in IE 8, as it is not possible to prettify them (to be able to set a break point for the appropriate statement). However, I have some doubts that supporting IE 8 is necessary for php.net. While I do understand that IE 8 is still in widespread use, I also do understand that it is an ancient browser (even if it was released in 2009) with a whole bunch of security issues. IMHO no developer should use it nowadays to surf the web (for whatever reason). BTW: the site has a conditional comment to include Remy Sharp's HTML5 shiv for *all* IE; that is most likely not *necessary* for recent versions (at least IE 11 is perfectly capable of handling HTML5, and even IE 9 might be). ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=66371 -- Edit this bug report at https://bugs.php.net/bug.php?id=66371&edit=1