Comment #5 on issue 819 by chris.ely: XSL Style Sheets not trimming trailing whitespace when using the <xsl:attribute> tag http://code.google.com/p/chromium/issues/detail?id=819
Jon, Thank you for the pointer to the spec. and for explaining about why the URL is coming up with character references. However, this does bring up a question about what Chrome is doing when it sees a URL with encoded characters. I've tried adding extra white space to the end of an image URL in the latest stable build. The result is that the trailing white space is stripped off the URL leaving me with a trimmed URL and the proper image. However, if I enter say "http://www.example.net/img.gif%20" the white space doesn't even seem to be decoded before being sent to the remote server. What is the proper behavior when translating spaces and/or other encoded characters in a URL? Is Chrome currently being consistent in this regard? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
