Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Insert a BOM check for import and file upload #348

Merged
merged 1 commit into from
Sep 11, 2014

Conversation

Martii
Copy link
Member

@Martii Martii commented Sep 10, 2014

  • Similar to @janekptacijarabaci fix in Show script source messes up character encoding greasemonkey/greasemonkey#1940 (Node.js via dev is currently using UTF-16 Big Endian strings from test file, mirrored at, notated from this comment)
  • Fix compliance with STYLEGUIDE.md and usage of pre-initialized identifiers
  • Currently do not propagate BOM (Byte Order Mark) with meta routine or user.js source with and without installation count increment (whoops it does the part striked out by default but everyone should get my point with the meta routine... e.g. doesn't appear to be needed in there)
  • BOM currently shows up in Ace as a exclamation triangle with "This character may get silently deleted by one or more browsers" on dev.

NOTE: Many thanks to the report by @cvzi and applies to #200 and partially outlined in #198.


Tested on dev with this script in Mozilla/5.0 (X11; Linux x86_64; rv:32.0) Gecko/20100101 Firefox/32.0

* Similar to @janekptacijarabaci fix in greasemonkey/greasemonkey#1940
* Fix compliance with STYLEGUIDE.md and usage of pre-initialized identifiers
* Currently **do not** propagate BOM with meta routine or user.js source with and without installation count increment
* BOM currently shows up in Ace as a exclamation triangle with "This character may get silently deleted by one or more browsers"

**NOTE**: Many thanks to the report by @cvzi and applies to OpenUserJS#200 and partially outlined in OpenUserJS#198.
@Martii Martii added bug You've guessed it... this means a bug is reported. CODE Some other Code related issue and it should clearly describe what it is affecting in a comment. DB Pertains inclusively to the Database operations. PR READY This is used to indicate that a pull request (PR) is ready for evaluation. and removed DB Pertains inclusively to the Database operations. labels Sep 10, 2014
Martii added a commit that referenced this pull request Sep 11, 2014
Insert a BOM check for import and file upload
@Martii Martii merged commit 1bf16e4 into OpenUserJS:master Sep 11, 2014
@Martii Martii deleted the insertBOMCheck branch September 11, 2014 16:50
@Martii Martii removed the PR READY This is used to indicate that a pull request (PR) is ready for evaluation. label Sep 11, 2014
Martii pushed a commit to Martii/OpenUserJS.org that referenced this pull request Oct 5, 2015
…keeps things consistent *hopefully*

* Using uppercase as mentioned at OpenUserJS#198 (comment)

Applies to OpenUserJS#678

Related to:
* OpenUserJS#348 discovery
* OpenUserJS#200
* OpenUserJS#198
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 23, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug You've guessed it... this means a bug is reported. CODE Some other Code related issue and it should clearly describe what it is affecting in a comment.
Development

Successfully merging this pull request may close these issues.

1 participant