18110 2008-03-26 09:30:12 -0700 xml document with x-mac-hebrew reports empty document? 2023-09-21 09:34:50 -0700 1 1 1 Unclassified WebKit XML 528+ (Nightly build) Mac OS X 10.5 RESOLVED CONFIGURATION CHANGED InRadar P2 Normal --- 1 eric webkit-unassigned ahmad.saleem792 annevk ap oldest_to_newest 75305 0 eric 2008-03-26 09:30:12 -0700 xml document with x-mac-hebrew reports empty document? I'm probably doing something wrong... See test case. 75307 1 20082 eric 2008-03-26 09:32:49 -0700 Created attachment 20082 test case 75308 2 eric 2008-03-26 09:33:35 -0700 If you remove the <?xml declaration then the document loads just fine. 75513 3 ap 2008-03-27 13:52:01 -0700 <rdar://problem/3977880> This is a tricky bug, and we are not aware of any actual sites that use this encoding (not counting test pages as real). 75610 4 ap 2008-03-28 02:42:34 -0700 I guess some more explanation is required :) See item 2 and the following item 1 of <ftp://ftp.unicode.org/Public/MAPPINGS/VENDORS/APPLE/HEBREW.TXT> - MacHebrew has '<' as an LTR character, which cannot be mapped to any single Unicode one, which is why decoding to UTF-16 inserts a direction override. The override rightfully confuses the parser, so this is really broken by design. 1978849 5 ahmad.saleem792 2023-09-20 18:02:39 -0700 Both Chrome Canary 119 and Safari 16.6, we get following: >> error on line 1 at column 44: Unsupported encoding x-mac-hebrew Do we need anything to do here? 1978934 6 annevk 2023-09-21 03:00:38 -0700 We're not going to support x-mac-hebrew on the web, however, there is a larger question here with what should happen with unknown encodings in XML. It doesn't appear to be specified in the XML specification. Chromium and WebKit agree on treating them as a fatal error, but Gecko renders the document. Minimal test: data:text/xml,<?xml%20version="1.0"%20encoding="a"?><b/> If at some point we decide to look at XML again maybe it's worth sorting this out. 1979027 7 ap 2023-09-21 08:39:32 -0700 I think that unknown encoding should probably be tracked as a separate bug. This one was very specifically about x-mac-hebrew when it was supported. What I'm not sure about is whether we have completely removed the support, or if it remains available in some circumstances, such as native apps perhaps. 1979040 8 annevk 2023-09-21 09:34:50 -0700 Renaming back and closing as it's no longer supported per Source/WebCore/PAL/pal/text/TextCodecICU.cpp. 20082 2008-03-26 09:32:49 -0700 2008-03-26 09:32:49 -0700 test case invalid-xml-x-mac-hebrew.xml application/xml 227 eric PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0ieC1tYWMtaGVicmV3IiA/Pgo8cm9vdD4KIDxm YWlsPiBUaGlzIGlzIHZhbGlkIHgtbWFjLWhlYnJldywgSSB0aGluaz8gPC9mYWlsPgogPHRlc3Qv PiA8IS0tIHNob3VsZG4ndCBldmVyIGJlIHBhcnNlZCwgYXMgdGhlIHBhcnNlciBzaG91bGQgYWJv cnQgYXQgdGhlIGZpcnN0IHNpZ24gb2Ygbm9uLXdlbGwtZm9ybWVkbmVzcyAtLT4KPC9yb290Pgo=