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

Edit report at https://bugs.php.net/bug.php?id=66371&edit=1 ID: 66371 Comment by: cmbecker69 at gmx dot de Reported by: TygerGilbert at USAWebAdv dot com Summary: JavaScript (I think) causing error on all pages Status: Open Type: Bug Package: Website problem Operating System: WinXP w/IE-8 PHP Version: Irrelevant Block user comment: N Private report: N New Comment: 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). Previous Comments: ------------------------------------------------------------------------ [2013-12-31 22:09:38] bjori@php.net That big blank area is normal. Its generated markup and we don't normalize the space. I'm out of ideas if those syntax changes I did in the js didn't make any difference, so we'll need someone on Windows to debug this. Unfortunately, I don't know of anyone :( ------------------------------------------------------------------------ [2013-12-31 21:33:04] TygerGilbert at USAWebAdv dot com Yes, it does. I went to Tools menu and turned on Developer Tools. A new frame opened up at the bottom. I set Debug on and ran the page script again. Another window opened up with the source in it. Trouble is, I have no idea what I'm looking at, or what I'm looking for right now. The left frame showing the script has a BIG blank area starting at line 256 (a <div class="partintro">...</div>) and going to line 851 (<h2>Table of Contents</h2>...), and there are no other large blank areas. This was after I selected [YES] to the "Do you want to stop..." dialog box, so maybe this was where the script that was terminated was located. When I select [No] to allow the script to continue, the dialog box immediately reappears. I'm sure this is of little help, but that's the best I can do. This is out of my area of expertise now. I just tried the page http://www.php.net/manual/en/ref.strings.php again (14:30 MST) and it still produces the error box. ------------------------------------------------------------------------ [2013-12-31 20:12:41] bjori@php.net Does IE have any sort of debug capabilities? This is a complete guessing game unless we can narrow it to the actual file/function that is causing this issue on IE. ...On that note, I did notice 2-3 syntax things that _could_ maybe cause problems in IE.. Could you try again in about an hour? ------------------------------------------------------------------------ [2013-12-31 16:13:19] TygerGilbert at USAWebAdv dot com Bjori@: Yes, I just now tried GoogleChrome and Mozilla Firefox to confirm, and neither of them showed an error dialog, and both of them displayed the link list on the left correctly. IE-8 shows the link list at the top full width and the documentation full width below that. In "Compatibility Mode," the error dialog does not appear. When not in Compatibilty Mode, the error occurs on every page (that I have tried) in the function list. The page layout is the same (wrong) regardless of being in Compatibility Mode or not. For example, the error dialog appears when I go to: http://www.php.net/manual/en/function.addslashes.php I must use WinXP because certain programs I use that are critical to my work do not function in Win-7 or Win-8 and no updates for them are available. IE-8 is the latest that is compatible with WinXP, so I can't update it. Using Chrome or Firefox is an option, but I prefer IE. Switching browsers just for PHP docs would leave me feeling annoyed with the site everytime. (This is irrelevant to fixing the error, but explains why I don't just change browsers.) ------------------------------------------------------------------------ [2013-12-31 09:19:20] bjori@php.net nl1 has been disabled for the passed few days due to other issues. Does this only happen in IE for you guys? (I can't reproduce this on other browsers, and don't have Windows) ------------------------------------------------------------------------ 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