12237 2007-01-12 18:58:02 -0800 Can't render ampersands in URLs if content type is application/xhtml+xml 2007-01-13 03:24:26 -0800 1 1 1 Unclassified WebKit Layout and Rendering 419.x Mac OS X 10.4 VERIFIED FIXED P2 Major --- 1 rmann webkit-unassigned oldest_to_newest 35279 0 rmann 2007-01-12 18:58:02 -0800 If I serve a page as "application/xhtml+xml", and include something like the following in the markup: <a href="SearchSubmit.do?t=e&fid=&ps=&p=2">next</a> Then the URI that Safari wants to go to is: http://localhost/dvd/SearchSubmit.do?t=e&fid=&%2338;ps=&%2338;p=2 However, if I serve it as "text/html", the URI is properly interpreted: http://localhost/dvd/SearchSubmit.do?t=e&fid=&ps=&p=2 If I try to build the URL using only ampersands, and not &, then if served as "application/xhtml+xml", Safari complains about the markup. Firefox behaves correctly on the exact same page. Top of the page is served with: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> 35288 1 12410 ddkilzer 2007-01-12 20:49:52 -0800 Created attachment 12410 Test case 35289 2 ddkilzer 2007-01-12 21:09:51 -0800 When I try to load Attachment 12410 in a locally-built debug build of WebKit r18818 with Safari 2.0.4 (419.3) on Mac OS X 10.4.8 (8L127), I don't see the problems you describe below. Can you attach a test case that reproduces the bug, or does Attachment 12410 reproduce this for you? Do you have any Haxies or InputManagers installed with Safari? 35290 3 ddkilzer 2007-01-12 21:12:09 -0800 Confirmed in shipping Safari 2.0.4 (419.3) on Mac OS X 10.4.8 (8L127). 35291 4 ddkilzer 2007-01-12 21:15:12 -0800 This issue has been fixed in WebKit ToT (tip of tree). You can try out a WebKit nightly build (download the DMG, mount it, then double-click on the WebKit icon) to verify that this is fixed: http://nightly.webkit.org/ 35292 5 rmann 2007-01-12 22:14:11 -0800 Yep, appears to work correctly in r18821. Thank you! (By the way, when does an update go out to everyone?) For the record, I have no Haxies nor InputManagers installed. The attached test case DOES reproduce the problem in 419.3. I was not sure what your comment (#3) meant: did you mean that you experienced the bug with it, or did you mean that you cannot reproduce it? 35236 6 ddkilzer 2007-01-13 03:24:26 -0800 (In reply to comment #5) > Yep, appears to work correctly in r18821. Thank you! (By the way, when does an > update go out to everyone?) See Bug 12199 Comment #3. > I was not sure what your comment (#3) meant: did you mean that you experienced > the bug with it, or did you mean that you cannot reproduce it? Comment #3 in this bug meant that I was able to reproduce the bug using shipping Safari. Sorry for any confusion! 12410 2007-01-12 20:49:52 -0800 2007-01-12 20:49:52 -0800 Test case bug-12237-test.xhtml application/xhtml+xml 316 ddkilzer PCFET0NUWVBFIGh0bWwgUFVCTElDICItLy9XM0MvL0RURCBYSFRNTCAxLjAgU3RyaWN0Ly9FTiIK ICAgICAgICAiaHR0cDovL3d3dy53My5vcmcvVFIveGh0bWwxL0RURC94aHRtbDEtc3RyaWN0LmR0 ZCI+CjxodG1sIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hodG1sIj4KPGhlYWQ+PHRp dGxlPjwvdGl0bGU+PC9oZWFkPgo8Ym9keT4KPGEgaHJlZj0iaHR0cDovL2J1Z3Mud2Via2l0Lm9y Zy9zaG93X2J1Zy5jZ2k/aWQ9MTIyMzcmYW1wO2N0eXBlPXhtbCZhbXA7Zm9vPWJhciI+QnVnIDEy MjM3IGFzIFhNTDwvYT4KPC9ib2R5Pgo8L2h0bWw+Cg==