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

BIDI doesn't work from mailto: shortcuts #66

Open
eyalpre opened this issue May 18, 2023 · 10 comments
Open

BIDI doesn't work from mailto: shortcuts #66

eyalpre opened this issue May 18, 2023 · 10 comments

Comments

@eyalpre
Copy link

eyalpre commented May 18, 2023

The BIDI does not work when creating new massage from mailto: shortcuts, while the Thunderbird application is not active.
I mean I have to open the application in background and just then pressing mailto: shortcuts will use BIDI on new massages..

@eyalroz
Copy link
Owner

eyalroz commented May 18, 2023

Which operating system?
Which TB version?
Which version of BiDi Mail UI?

Also: What do you get in the Error Console when you do this?

@eyalpre
Copy link
Author

eyalpre commented May 18, 2023

Win10, TB 102.11.0 (64 bit), BIDI ver 0.13
I do not get any error - there are no RTL buttons or option to write in RTL in the new message window...
It works ok when I compose new message while TB is on (even messege using mailto shortcut)..

@eyalroz
Copy link
Owner

eyalroz commented May 18, 2023

I mean, please choose "Tools | Mail & Newsgroups" on the menu, then in the main window which opens up, choose "Tools | Developer Tools | Error Console" on the menus. That's how you check for errors.

@eyalpre
Copy link
Author

eyalpre commented May 18, 2023

Content Security Policy: The page's settings blocked the loading of a resource at inline ("default-src").

@eyalpre
Copy link
Author

eyalpre commented May 18, 2023

Exception { name: "NS_ERROR_NOT_AVAILABLE", message: "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIDocShell.domWindow]", result: 2147746065, filename: "resource://devtools/server/actors/targets/window-global.js", lineNumber: 422, columnNumber: 0, data: null, stack: "get window@resource://devtools/server/actors/targets/window-global.js:422:5\n_navigate@resource://devtools/server/actors/targets/window-global.js:1532:24\nDebuggerProgressListener.prototype.onStateChange<@resource://devtools/server/actors/targets/window-global.js:1918:27\nexports.makeInfallible/<@resource://devtools/shared/ThreadSafeDevToolsUtils.js:103:22\n", location: XPCWrappedNative_NoHelper }
ThreadSafeDevToolsUtils.js:82:13

@eyalpre
Copy link
Author

eyalpre commented May 18, 2023

Is that helps ?

@eyalroz
Copy link
Owner

eyalroz commented May 18, 2023

Ok, that's something to work with. If I haven't gotten back to you in a ... say, week, please ping me.

@eyalpre
Copy link
Author

eyalpre commented May 18, 2023 via email

@eyalpre
Copy link
Author

eyalpre commented May 25, 2023

Any progress ?

@eyalroz
Copy link
Owner

eyalroz commented May 26, 2023

(sigh) not really, I've been both busy and not feeling too well...

I can at least say I can reproduce the issue. The question is what I can do about it. I need more time.

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

No branches or pull requests

2 participants