1018050 - PHP errors in comments push character encoding declaration beyond the first 1024 bytes when searching on freearabicdictionary.com

Status: RESOLVED WORKSFORME

(Web Compatibility :: Site Reports, defect)

Description

[Filip Filipović]

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:32.0) Gecko/20100101 Firefox/32.0 (Beta/Release)
Build ID: 20140529113510

Steps to reproduce:

Go to http://www.freearabicdictionary.com/ and type a word in Arabic, for example شَجَرَة 


Actual results:

Firefox detects Western encoding and the text is unreadable.


Expected results:

The correct encoding is Unicode and manually setting it to Unicode makes the page readable. Internet Explorer 11 correctly detects the encoding.

Comment 1

[:Gijs (he/him)]

Henri, you seem like the most likely person to know more about what's going on here, can you help? :-)

To be clear, STR:
1. Open http://www.freearabicdictionary.com/
2. Copy-paste the arabic from comment #0
3. Click Search


Oddly enough, closing the tab and reopening it (ctrl/cmd-shift-t) makes the issue go away.

Comment 2

[Henri Sivonen (:hsivonen)]

This site dumps PHP errors in a comment that precedes the HTML markup. When performing a search, the PHP errors are numerous enough that the character encoding declaration is pushed beyond the first 1024 bytes of the document. Since the search query is performed using HTTP POST, Firefox won't reload the page when discovering the character encoding declaration later in the document.

The site should get rid of its PHP errors (or declare the encoding on the HTTP layer to make the PHP errors not matter).

Comment 3

[Mike Taylor [:miketaylr]]

Attachment: Screen Shot 2017-04-07 at 12.44.42 PM.png

AFAICT, this has been fixed by the site.