Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Αυτός ο ιστότοπος θα έχει περιορισμένη λειτουργικότητα, όσο εκτελούμε εργασίες συντήρησης για να βελτιώσουμε την εμπειρία σας. Αν ένα άρθρο δεν επιλύει το ζήτημά σας και θέλετε να κάνετε μια ερώτηση, η κοινότητα υποστήριξής μας είναι έτοιμη να σας βοηθήσει στο Twitter (@FirefoxSupport) και στο Reddit (/r/firefox).

Αναζήτηση στην υποστήριξη

Προσοχή στις απάτες! Δεν θα σας ζητήσουμε ποτέ να καλέσετε ή να στείλετε μήνυμα σε κάποιον αριθμό τηλεφώνου ή να μοιραστείτε προσωπικά δεδομένα. Αναφέρετε τυχόν ύποπτη δραστηριότητα μέσω της επιλογής «Αναφορά κατάχρησης».

Μάθετε περισσότερα

Indent button in compose window doesn't indent, it quotes

  • 1 απάντηση
  • 0 έχουν αυτό το πρόβλημα
  • 1 προβολή
  • Τελευταία απάντηση από Matt

more options

It appears that the indent/unindent button in the message composer doesn't indent and unindent, it increases and decreases the blockquote level. Quoting and indenting are different operations, and need to be formatted differently. I see that pressing the indent button uses a < blockquote> while "real" quoting uses < blockquote type=cite>. You would think it possible to add CSS to properly differentiate between the two.

Unfortunately email clients like Gmail and Outlook don't support attribute selectors in CSS. That means that it's impossible for the recipients using Gmail and Outlook to differentiate between quotes and indents. Composing emails that don't render properly on Gmail and Outlook is just not a practical option. Very few (probably none) of the people to which I send emails are running Thunderbird. I need quote and indent to work with recipients that aren't running Thunderbird.

According to multiple sources I've found, the blockquote tag has been frowned upon for a long, long time when what you want is indent. The proper way to indent is < div style="pad-left: 3em" > or < div style="left-margin: 3m" >.

Would it be possible to fix the indent button so that it doesn't quote the selected text, it indents it?

It appears that the indent/unindent button in the message composer doesn't indent and unindent, it increases and decreases the blockquote level. Quoting and indenting are different operations, and need to be formatted differently. I see that pressing the indent button uses a < blockquote> while "real" quoting uses < blockquote type=cite>. You would think it possible to add CSS to properly differentiate between the two. Unfortunately email clients like Gmail and Outlook don't support attribute selectors in CSS. That means that it's impossible for the recipients using Gmail and Outlook to differentiate between quotes and indents. Composing emails that don't render properly on Gmail and Outlook is just not a practical option. Very few (probably none) of the people to which I send emails are running Thunderbird. I need quote and indent to work with recipients that aren't running Thunderbird. According to multiple sources I've found, the blockquote tag has been frowned upon for a long, long time when what you want is indent. The proper way to indent is < div style="pad-left: 3em" > or < div style="left-margin: 3m" >. Would it be possible to fix the indent button so that it doesn't quote the selected text, it indents it?

Τροποποιήθηκε στις από το χρήστη Matt

Όλες οι απαντήσεις (1)

more options

Ok I have hacked your HTML to prevent it from rendering.

Now lets look at this.

You say
Unfortunately email clients like Gmail and Outlook don't support attribute selectors in CSS.

Wonderful, except they really do not support style either in the head or in the body over a google.

See https://www.campaignmonitor.com/css/style-element/style-in-head/  

If your goal is maximum folk seeing what you write how you format it. CSS is not a very functional option in email is the short answer.

https://bugzilla.mozilla.org/show_bug.cgi?id=882181 is the bug for this issue, not the support forum as it is not a support issue.