copyright symbol used anywhere in a content script breaks extensions in Edge

Not reproducible Issue #10172350

Details

Author
K H.
Created
Dec 13, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
38.14393
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Including the © symbol anywhere in a content script file prevents all code in that file from doing anything.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

      Changed Assigned To to “Sermet I.”

      Changed Assigned To from “Sermet I.” to “Scott L.”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed” to “Not reproducible”

    • Hi! Thanks for filing this bug. I wrote a test extension with the following as a content script and unfortunately was not able to reproduce this issue:

      // ©
      alert(‘©’);
      alert(‘running?’);

      Both alerts appeared as expected when I ran that code in Edge on build 14393.594. Adding the line var © = ‘hello’ breaks everything as you described, but it does this in both Edge and Chrome in regular scripts as well as extension scripts. Is this the behavior you’re referring to? If so, I believe this is by design.

      If you’re seeing some other behavior, please reopen this issue and attach some sample code so we can take a look at what’s going on. Thanks again!

    • Changed Status from “Not reproducible”

    • Do we know why this was first marked confirmed (Ted D) and then marked not reproducible by someone else (Scott L)?

      Anyway, steps to reproduce…

      Go to https://github.com/fiendish/SaveTextFilesInEdge and download the zip of the repository. Or directly get https://github.com/fiendish/SaveTextFilesInEdge/archive/master.zip

      If the name of the repository is unclear, this is an extension for Edge that lets you save currently navigated text files, because Edge currently only lets you save certain file types (that is absolutely insane, by the way. fire the person who did that and hire me instead).

      Extract and load the folder as an extension in Edge 14393 or 14959*

      Close Edge and re-launch it, because Edge doesn’t automatically activate newly installed extensions (I would also call this a bug. is it known/filed?).

      Accept the new message about running extensions.

      Navigate to https://raw.githubusercontent.com/fiendish/SaveTextFilesInEdge/master/testfiles/%C8%A7%C3%A4.txt

      Alternate click on the page and you should see a new context menu item called “Save Page Text…”

      If you choose it you will see that the content of the page opens in Notepad (this is another bug, in msSaveBlob on “known” file types, but that one is already being tracked).

      NOW…

      Uninstall the extension. Edit the second line of content-script.js so that instead of reading
      "* Copyright 2016 Avi Kelman "
      it instead reads
      "* Copyright © 2016 Avi Kelman "

      Notice that this change is inside a comment.

      Save the change, reinstall the extension, close and re-open Edge (again because it doesn’t seem to activate freshly installed extensions).

      Now navigate again to https://raw.githubusercontent.com/fiendish/SaveTextFilesInEdge/master/testfiles/%C8%A7%C3%A4.txt

      Right click again. Choose “Save Page Text…” again. And notice that this time nothing happens.

    • I just tested 14986, and now the situation is even worse. 14986 edge crashes when calling msSaveBlob.

    • I don’t think I can edit comments, sorry about the multiple updates.
      I’ve filed a bug about the crash ( https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/10396033/ ).
      For now you’ll have to test in 14959.

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

      Changed Status to “Not reproducible”

    • Thank you for the update. We will follow up in the provided link.

    You need to sign in to your Microsoft account to add a comment.

    Sign in