Robert Kaiser wrote:
Rufus wrote:
Well, for one - as the interface stands now I have no idea what the
JavaScript default is for Mail and News by just reading the Prefs panel;
only that it is enabled or disabled for the Browser. So the assumption
could be that if I enable it for the Browser, it's now enabled globally.
If it was globally, it wouldn't state "Browser" next to the checkbox.
Not having a checkbox to enable it for mail and newsgroups means that
you cannot enable it, i.e. it's not available at all. But I agree that
the user interface could be better. I'd appreciate a bug with
suggestions and a patch filed for 2.1.
...I was code head of sorts...in a previous life...to me it's "implied"
because it doesn't say anything now and did before, and in my
professional life we aren't in the habit of taking functionality out of
code - or at least we don't NOOP it without making it clear what the new
result is. So my impression was that something was still happening
behind the scenes for Mail and News that I now no longer have control over.
Poor interface design; no feedback/information on what is going on. And
suppose I do want it enabled for Mail and News...then what is my option?
None. JavaScript in MailNews is not just evil, it's not supported due to
its unclear security state.
Wish it told me that someplace. I'm big on security features - also
from a professional standpoint. The flexibility and user options in SM
are one of it's stronger facets, IMO.
For all the others, have youu looked if bugs are filed? Can you help
with putting some of your own time in and work on any of them yourself?
We are a volunteer project, most things only happen if someone
volunteers for them, you know...
No - the other items I've listed defiantly fall into the category of
enhancements, not bugs. It also appears that the information in SM Help
is ahead of the release in a number of areas/implementations.
Enhancements are also "bugs" in Mozilla speak, i.e. they need a bug
report filed in Bugzilla to be tracked. Anything just mentioned anywhere
else is pretty sure to fall through the cracks, and any code change
whatsoever needs a bug report where it was discussed to be mentioned in
its commit comment.
Ahhh...at work we make a distinction. I'll look into capturing all my
observations in bug reports on Bugzilla, then. If it'll help, I'd be
happy to. I read in another thread that coders were reading/monitoring
here and to keep posting. So I have been.
I'm not a coder so I can't contribute that way, but I do evaluate
software interfaces and operation professionally. I should probably be a
beta tester...I could at least help out that way.
Any help would be appreciated!
And you probably also could be a "bug" reporter :)
Robert Kaiser
I'll try a swing at it.
--
- Rufus
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
