Re: browse-url-of-buffer broken at HEAD?

["T.V Raman" <raman@google.com>]

"T.V Raman" <raman@google.com> writes:
Additional info:

Restoring browse-url.el from early April makes the problem go away ---
suspect this breakage comes from the recent changes in browse-url to
 allow multiple handlers. I failed to spot the cause after staring at
 the diff 
> Simple Test Case:
>
> 1. Create  a new empty buffer  called "foo" and switch to it
> 2. Type this in that buffer:
> <p>test</p>
> 3. M-x browse-url-of-buffer
> where browse-url is set up to render using EWW
> 4. You dont get a rendered result, instead you see the HTML source,
> and a message in the minibuffer re loading the HTML5 schema.
> 5. But if you now switch to *Messages* you see an error
> "File exists but cannot be read".
> 6. /tmp does contain the generated file, and eww-open-file renders it
> correctly.
>
> Might be useful when debugging, if you  again try
> browse-url-of-buffer, you dont see the error message above (but you
> dont get the result rendered either)
>
> Using debug-on-error did not help, it did not enter the debugger.
>
> This error appears relatively new,
>
>
>
> -- 

--