Network bug triager here.  After a cursory code search, I'm re-assigning the component, on the basis that it is generated from  FrameFetchContext::printAccessDeniedMessage(), for further triage.

I'm closing this for now until we get more information.

When I load https://rawgit.com/fprades/chrome-xslt-issue/master/file.xml I see the stylesheet is loaded and applied. It fails, complaining of trailing content (open the page in the inspector and look at the DOM), but you see the title is "success", etc.

Maybe this was a regression that was fixed? Until we get a repro failing in a specific version it is hard to track this down further.

I don't understand why this is closed as won't fix. I'm not sure who should provide more info. Before closing should ask for more info. Marking as won't fix looks like won't be addressed ever. I'm interested in getting this fixed and track it. Please can you reopen?

Anyone is welcome to provide more information. The Needs-Feedback label means we'd like more information. rnimmagadda: it might be worth briefly explaining what's needed when adding the label.

safull, I looked at your bug report and I think the only problem here is the error message about your XML--trailing content--is inserted in the HEAD element which makes it not appear. It's not ideal, but you can use Inspector to look at the DOM and see the error message. Unfortunately we don't have the resources to improve how XML error messages are displayed.

Hi dominicc,

I've been reviewing the issue. I finally found the root cause: it's due to the header Content-Security-Policy.

Content-Security-Policy: sandbox; default-src 'none'; img-src 'self'; style-src 'self';

Which was disabling xslt processing.

Ah! Good sleuthing. Glad you worked it out.