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

i can solve problems #586

Open
wants to merge 753 commits into
base: chrome-selective-menuitem
Choose a base branch
from
Open

i can solve problems #586

wants to merge 753 commits into from

Conversation

sohaibabbas
Copy link

please share the code

adam-p and others added 30 commits October 25, 2013 22:33
…ogging.

Prompted by a user report (https://groups.google.com/forum/#!topic/markdown-here/ikXFqkP77Ws) of Firefox options access errors. Couldn't reproduce, so no idea if this fixes the problem.
…g. Now making request to background script.
…fine in Chrome. Some debug code and text still present
… translations. Added translators section to CONTRIBUTE.md
…e now sorted to help minimize diff noise (going forward).
adam-p and others added 30 commits May 13, 2017 17:47
This is related to #173, but the fix for that didn't check deeply enough.
This seemed to occur in Chrome on all pages, and in Firefox on some pages (Gmail, but not the contenteditable test page).
I had messed up the generation of it, then didn't read it carefully -- there were values missing from it.
Forgot-to-Render check for Fastmail
- CSS for the preference dialogs has moved
- NsISupportsString in setComplexValue() has been dropped in favour of setStringPref()
- Thunderbird 60 refusing explicit decliration of option type 1 in install.rdf
And copy over some linting stuff from the defunct xul branch.
Fix #495: Stopped working in Thunderbird 60
A string added in the Firefox 60 fix wasn't copied to the non-English `messages.json` files, which meant that it wasn't in the non-English `strings.properties` and `string.dtd` files. This caused Thunderbird to not load the overlay in Thunderbird, which prevented it from being present in the message window.

To help mitigate this in the future, to some degree, the `i18n.js` script makes sure that all English strings are present in the other languages when creating the the .properties and .dtd files. But I still have to remember to run that script.
Fix #524 and #526: Broken in non-English Thunderbird
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet