XML files no longer seem to handle javascript events. Additionally right-click copy/paste are disabled.
Reported by
alan.str...@gmail.com,
May 24 2018
|
|||||||
Issue descriptionChrome Version : 66.0.3359.139 URLs (if applicable) : all XML-based URLS (http, file, etc.) Other browsers tested: N/A What steps will reproduce the problem? (1) Open XML file (preferably with XML Tree extension installed) (2) Click on any XML node and no action takes place even though click listeners are there. With the extension installed, the xpath to the node will appear in the text-area at the top. (3) Additionally, highlight text and attempt to right-click to copy (no extension required). What is the expected result? XML documents should be treated the same as HTML with full access to javascript events and copy/paste via context menu. What happens instead? Nothing happens. Debugging via developer tools shows no event is being fired in chrome-extension://gbammbheopgpmaagmckhpjbfgdfkpadb/utils.js I'm the extension developer and have noticed the copy/paste issue for a few months. As keyboard shortcuts still work, it wasn't that pressing of an issue. Now with recent versions of Chromium, the click and double-click events appear to be disabled.
,
May 25 2018
,
May 25 2018
Tested the issue on chrome reported version 66.0.3359.139 using Mac 10.12.6 with steps mentioned below: 1) Launched chrome reported version and installed "XML Tree" extension 2) Loaded sample XML file on chrome, highlighted the note and right clicked on it, copy is disabled @Reporter: Please find the attached screencast for your reference and let us know if you are observing the same which i have captured in screencast and provide your feedback on it which help in further triaging it. Thanks!
,
May 25 2018
The screencast shows the issue for the copy/paste being disabled in the context menu. The other issue of document.body.onclick (ondblclick, onmouseover, etc.) not being fired is not shown.
,
May 25 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 31 2018
Able to reproduce the issue on Mac 10.13.3, Win-10 and Ubuntu 14.04 using chrome latest stable #67.0.3396.62 and latest canary #69.0.3445.2. This is a non-regression issue as it is observed from M60 old builds. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
May 31 2018
Events not firing is not a V8 issue. I'm guessing Blink>XML might be a better component for this?
,
May 31 2018
To get the onclick, ondblclick, etc. events working, I was able to change the extension to put the generation and adding of the <script> tag in the content script instead of the stylesheet I use to generate the HTML version of the XML document, and it worked.
Version 2.0.1
<script type="text/javascript" src="{$utilsPath}"></script>
where the $utilsPath is a parameter passed to the stylesheet from the content script
processor.setParameter(null, 'utilsPath', chrome.extension.getURL('utils.js'));
Version 2.0.2
var utilsScript = document.createElementNS(xhtmlNS, 'script');
utilsScript.setAttribute('src', chrome.extension.getURL('utils.js'));
(document.head || document.documentElement).appendChild(utilsScript);
The end results is the exact same HTML document being served up, but for whatever reason, the browser does not recognize the the <script> tag or maybe its src attribute in version 2.0.1. I tried moving the the <script> tag out of the <head> and after/right-before the closing </body> tag but it didn't make a difference. Seems silly.
,
Jul 25
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by alan.str...@gmail.com
, May 24 2018