-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Message document rendering ignores our injected stylesheet #20
Comments
Status so far:
|
eyalroz
pushed a commit
that referenced
this issue
Aug 12, 2020
* Workaround for ignored stylesheets - now injecting style elements as text * Changed the previously-implemented link injectors to create non-HTML elements (`createElement()` with no namespace) - so that it triggers the security error - but at least there's an _attempt_ to load the sheet.
eyalroz
pushed a commit
that referenced
this issue
Aug 12, 2020
* Workaround for ignored stylesheets - now injecting style elements as text * Changed the previously-implemented link injectors to create non-HTML elements (`createElement()` with no namespace) - so that it triggers the security error - but at least there's an _attempt_ to load the sheet.
eyalroz
pushed a commit
that referenced
this issue
Aug 13, 2020
* Workaround for ignored stylesheets - now injecting style elements as text * Changed the previously-implemented link injectors to create non-HTML elements (`createElement()` with no namespace) - so that it triggers the security error - but at least there's an _attempt_ to load the sheet.
eyalroz
pushed a commit
that referenced
this issue
Aug 14, 2020
…ment (and no need for the workaround) * Removed the style-element-with-no-link workaround code. * Other changes to the stylesheet-link-adding function; specifically, still using a non-namespaced link element. * Apparently, Thunderbird _is_ willing to use linked chrome in content documents if it's via a `resource://` URI; so - doing that: * Registering our chrome folder for use as a "resource" * Tweaked the stylesheet injector function to use a `resource://` URI
eyalroz
pushed a commit
that referenced
this issue
Aug 14, 2020
* Workaround for ignored stylesheets - now injecting style elements as text * Changed the previously-implemented link injectors to create non-HTML elements (`createElement()` with no namespace) - so that it triggers the security error - but at least there's an _attempt_ to load the sheet.
eyalroz
pushed a commit
that referenced
this issue
Aug 14, 2020
…ment (and no need for the workaround) * Removed the style-element-with-no-link workaround code. * Other changes to the stylesheet-link-adding function; specifically, still using a non-namespaced link element. * Apparently, Thunderbird _is_ willing to use linked chrome in content documents if it's via a `resource://` URI; so - doing that: * Registering our chrome folder for use as a "resource" * Tweaked the stylesheet injector function to use a `resource://` URI
eyalroz
pushed a commit
that referenced
this issue
Aug 16, 2020
* Workaround for ignored stylesheets - now injecting style elements as text * Changed the previously-implemented link injectors to create non-HTML elements (`createElement()` with no namespace) - so that it triggers the security error - but at least there's an _attempt_ to load the sheet.
eyalroz
pushed a commit
that referenced
this issue
Aug 16, 2020
…ment (and no need for the workaround) * Removed the style-element-with-no-link workaround code. * Other changes to the stylesheet-link-adding function; specifically, still using a non-namespaced link element. * Apparently, Thunderbird _is_ willing to use linked chrome in content documents if it's via a `resource://` URI; so - doing that: * Registering our chrome folder for use as a "resource" * Tweaked the stylesheet injector function to use a `resource://` URI
eyalroz
pushed a commit
that referenced
this issue
Sep 5, 2020
* Workaround for ignored stylesheets - now injecting style elements as text * Changed the previously-implemented link injectors to create non-HTML elements (`createElement()` with no namespace) - so that it triggers the security error - but at least there's an _attempt_ to load the sheet.
eyalroz
pushed a commit
that referenced
this issue
Sep 5, 2020
…ment (and no need for the workaround) * Removed the style-element-with-no-link workaround code. * Other changes to the stylesheet-link-adding function; specifically, still using a non-namespaced link element. * Apparently, Thunderbird _is_ willing to use linked chrome in content documents if it's via a `resource://` URI; so - doing that: * Registering our chrome folder for use as a "resource" * Tweaked the stylesheet injector function to use a `resource://` URI
eyalroz
pushed a commit
that referenced
this issue
Sep 5, 2020
* Workaround for ignored stylesheets - now injecting style elements as text * Changed the previously-implemented link injectors to create non-HTML elements (`createElement()` with no namespace) - so that it triggers the security error - but at least there's an _attempt_ to load the sheet.
eyalroz
pushed a commit
that referenced
this issue
Sep 5, 2020
…ment (and no need for the workaround) * Removed the style-element-with-no-link workaround code. * Other changes to the stylesheet-link-adding function; specifically, still using a non-namespaced link element. * Apparently, Thunderbird _is_ willing to use linked chrome in content documents if it's via a `resource://` URI; so - doing that: * Registering our chrome folder for use as a "resource" * Tweaked the stylesheet injector function to use a `resource://` URI
eyalroz
pushed a commit
that referenced
this issue
Sep 5, 2020
* Workaround for ignored stylesheets - now injecting style elements as text * Changed the previously-implemented link injectors to create non-HTML elements (`createElement()` with no namespace) - so that it triggers the security error - but at least there's an _attempt_ to load the sheet.
eyalroz
pushed a commit
that referenced
this issue
Sep 5, 2020
…ment (and no need for the workaround) * Removed the style-element-with-no-link workaround code. * Other changes to the stylesheet-link-adding function; specifically, still using a non-namespaced link element. * Apparently, Thunderbird _is_ willing to use linked chrome in content documents if it's via a `resource://` URI; so - doing that: * Registering our chrome folder for use as a "resource" * Tweaked the stylesheet injector function to use a `resource://` URI
eyalroz
pushed a commit
that referenced
this issue
Sep 5, 2020
* Workaround for ignored stylesheets - now injecting style elements as text * Changed the previously-implemented link injectors to create non-HTML elements (`createElement()` with no namespace) - so that it triggers the security error - but at least there's an _attempt_ to load the sheet.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the TB-78-compatible - injected - versions, direction autodetection fails quietly; not sure why.
The text was updated successfully, but these errors were encountered: