On Nov 19, 2015, at 9:53 AM, Walter Lee Davis <
wa...@wdstudio.com> wrote:
>
> On Nov 19, 2015, at 8:23 AM, Walter Lee Davis <
wa...@wdstudio.com> wrote:
>
>>>
>>> On Nov 19, 2015, at 7:16 AM, 'Robert Klemme' via nokogiri-talk <
nokogi...@googlegroups.com> wrote:
>>>
>>> On Thu, Nov 19, 2015 at 11:37 AM, Shivasubramanian A
>>> <
ashivasu...@gmail.com> wrote:
>>>> Hello Robert,
>>>>
>>>>> Verified. Additionally I changed parameter names to make the second one
>>>>> "q" and Google's search page properly shows the value in the search bar on
>>>>> the results page.
>>>>
>>>> Does that mean you accept that this is a bug? Or do you have a possible
>>>> workaround? Your reply is ambiguous.
>>>
>>> I said Nokogiri works as expected - that clearly means "no bug". You
>>> seem to be the only one having an issue. I cannot reproduce it.
>>>
>>> robert
>>>
>>>
>>
>> In XHTML Strict, having an unescaped ampersand anywhere in your code, even in a url, makes the page invalid.
>
> Even in HTML5:
http://scripty.walterdavisstudio.com/link-test.html
Sorry to bang on about this; by saying Even in HTML5, I don't mean that it is invalid in HTML5. HTML5 took the "pave the cowpaths" approach of making every "wrong" (by XHTML Strict standards) thing that people were doing already in millions and billions of Web pages, and declaring them legal. So there are a lot of things you can get away with in HTML5 that would be laughable in a stricter DOCTYPE. Un-closed (closed by inference only) tags: I am looking at you! I cut my teeth on XHTML Strict, so I use that syntax out of muscle memory or sheer pig-headedness.