Frequently-Asked Questions

Automatic Direction Detection

I've received this message, and the extension did not set its direction correctly. Why?

This could be due to one of the following:

  • Mozilla has mis-detected the message encoding, so the extension is not aware that there are actually any RTL-script characters in the message.
  • Your message contains both RTL and LTR text, and the detection algorithm simply works differently than your intuition for the message.
  • The message is in HTML rather than plain text.
  • You have set the mailnews.message_display.autodetect_direction preference to false, disabling automatic message direction detection.

Keyboard Behavior

Why does direction switching not use the keyboard shortcuts Ctrl+LeftShift and Ctrl+RightShift, like in Microsoft Windows and popular Hebrew keyboard layouts for X?

We are hoping to eventually do so, but we are not yet able to, due to problems in keyboard input handling in Mozilla.


Miscellany

I noticed that some code from the BiDi Browser UI extension was incorporated into the Mozilla codebase. Can we expect this to happen with this extension also? How soon?

That's a very perceptive question... it is possible that code adoption will also happen with this extension at some point in the future. This issue is open for discussion on the IRC channel #bidi@moznet.


Why does the extension change the behavior of the Enter key? I want the default 'Body Text'-style behavior back...

You can revert to the default Enter key behavior by setting the preference:

pref("mailnews.alternative_enter_behavior", false);


When I write HTML messages in Paragraph mode, I can't figure out where I have paragraph transitions and where there's just a line break. What can I do?

You can have a visual indication of paragraph ends by adding an appropriate rule to userContent.css:

body[_moz_dirty] p:after { content: "\B6"; }

This is actually the character ¶ (the escaping is for avoiding charset issues if your .css file isn't UTF-8 encoded).


I have another issue which is not covered in this FAQ...

That's great! Submit a bug in our bugs section. Make sure to give as much detail as possible, and provide instructions for reproducing your problem.