MozillaZine

How to completely remove preview pane in Mail?

User Help for Seamonkey and Mozilla Suite
barbaz
 
Posts: 1589
Joined: October 1st, 2014, 3:25 pm

Post Posted July 10th, 2015, 11:01 am

Running SeaMonkey 2.30 for Mail (can't upgrade that atm) on this OS. I would like the Preview pane to be completely gone, so I have it deselected. However, when I first start Mail, it shows up as the splitter on the bottom of the window - and I just discovered that it's actually "there" and appears to be opening emails while in that state :shock:
(I found that out when marking an email as Junk, it popped up from the bottom with an infobar saying it thinks this message is Junk.)

It appears to be completely gone if I check and then un-check the option for it in the View menu, but on looking with DOM Inspector, I'm not sure it isn't just hidden...

Short of writing an extension, is there some way to always have it completely gone? I don't want to be opening emails just by selecting them.

TIA
*Always* check the changelogs BEFORE updating that important software!

Andy Boze

User avatar
 
Posts: 2755
Joined: June 30th, 2005, 9:53 pm
Location: South Bend, IN

Post Posted July 10th, 2015, 3:25 pm

But then again, I may be wrong.

barbaz
 
Posts: 1589
Joined: October 1st, 2014, 3:25 pm

Post Posted July 10th, 2015, 6:08 pm

Thanks Andy Boze for digging those bugs up. So it looks like I will need to have some kind of extension.

(Hmm... I wonder if there would be adverse effects from using an extension to actually remove the preview pane's nodes... I'll have to try that later. And I wonder, assuming it's fine, whether that will also do anything for that training.dat problem I had posted about before... :-k )
*Always* check the changelogs BEFORE updating that important software!

Frank Lion

User avatar
 
Posts: 19108
Joined: April 23rd, 2004, 6:59 pm
Location: ... The Exorcist....United Kingdom

Post Posted January 3rd, 2017, 5:57 pm

barbaz wrote: :-k )

Try (in userChrome.css under namespace) -

Code: Select all
#messagepanebox { display: none !important;}


Just depends what your definition of hidden is. This 100% vanishes that pane, whereas grippys, etc. just hide it, leaving it waiting to fly out again to startle the unsuspecting at unexpected moments. For all I know, just vanishing it so that you and everybody else never see it again, might well be good enough.

As you said, you can hit the nodes, but doing that also tends to hit the fan elsewhere, in my experience.

I've left the threadpane splitter visible here, just so you can see what's going on.
Metal Lion latest SeaMonkey & Thunderbird Themes - Sea Monkey and Silver Sea Monkey
"The only thing necessary for the triumph of evil, is for good men to do nothing." - Edmund Burke (attrib.)

barbaz
 
Posts: 1589
Joined: October 1st, 2014, 3:25 pm

Post Posted January 3rd, 2017, 7:31 pm

Thanks Frank, I'll add that and see how it goes. 8-)
*Always* check the changelogs BEFORE updating that important software!

Frank Lion

User avatar
 
Posts: 19108
Joined: April 23rd, 2004, 6:59 pm
Location: ... The Exorcist....United Kingdom

Post Posted January 3rd, 2017, 7:42 pm

barbaz wrote:Thanks Frank, I'll add that and see how it goes. 8-)

Yeah, let me know, as I can see what you mean and reproduced it -

(I found that out when marking an email as Junk, it popped up from the bottom with an infobar saying it thinks this message is Junk.)


Seriously, just how dumb is that guy inside SeaMonkey? I know it's junk, it was me that just marked it as junk!
Metal Lion latest SeaMonkey & Thunderbird Themes - Sea Monkey and Silver Sea Monkey
"The only thing necessary for the triumph of evil, is for good men to do nothing." - Edmund Burke (attrib.)

barbaz
 
Posts: 1589
Joined: October 1st, 2014, 3:25 pm

Post Posted January 3rd, 2017, 9:22 pm

Frank Lion wrote:
barbaz wrote:Thanks Frank, I'll add that and see how it goes. 8-)

Yeah, let me know,

As I've just discovered when trying to read the email notification of your reply, that CSS needs to be wrapped in a @-moz-document. Otherwise it hides messages opened in a new window too.

So now I have this -
Code: Select all
@-moz-document url("chrome://messenger/content/messenger.xul") {
  /* Frank hide preview pane ..........*/
  #messagepanebox { display: none !important;}
}


Most spam filtering here is done server side these days, so it may take me a while to report back.
*Always* check the changelogs BEFORE updating that important software!

Frank Lion

User avatar
 
Posts: 19108
Joined: April 23rd, 2004, 6:59 pm
Location: ... The Exorcist....United Kingdom

Post Posted January 4th, 2017, 8:13 am

barbaz wrote:As I've just discovered when trying to read the email notification of your reply, that CSS needs to be wrapped in a @-moz-document. Otherwise it hides messages opened in a new window too.

Yeah, this isn't a great fix and I don't think it can be done properly with just .css.

The #messagepanebox's node is the notificationbox and there is nothing conditional that I can grab hold of there. That doesn't come until further down the stack when you get this -
notification[value="junkContent"] but I can only make use of that condition further down the stack, not higher up in it. It's just how this stuff works.

That means that .css fixes are always going to be a scattergun approach that can't be made conditional on just junk passing into the Junk folder.

It seems that even if you have the Preview Pane turned off, then any notification after that, er, turns it on and it stays on.
Metal Lion latest SeaMonkey & Thunderbird Themes - Sea Monkey and Silver Sea Monkey
"The only thing necessary for the triumph of evil, is for good men to do nothing." - Edmund Burke (attrib.)

Return to SeaMonkey Support


Who is online

Users browsing this forum: No registered users and 1 guest