Print on the Firefox context menu

And on the seventh day Gervase Markham spoke:

>> I may disagree with a lot of things. But messing
around with developed
>> content that is not your own is not something that
should be done
>> deliberately with the exception of security or
major usability
>> considerations.
>
>Rubbish. We allow it in lots of places. "Use own
fonts and colours". 
>"Set Text Size".

What in "major usability concerns" did you not
understand?

>The entire point of Greasemonkey is to mess around with 
>developed content that is not your own.

Greasemonkey is an extension. And there are valid reasons
why it is not
included by default.

>Anyway, not being able to Print, Find or read what you
are looking at 
>are major usability concerns.

Great.

>> I don't know which browser you are using, but on my
Firefox 2 it's a
>> global setting (per session). Once I change the
text size, it is also
>> adjusted on other pages I visit later.
>
>...in the same window.

Since we have a tabbed interface, I consider this to be
enough.

>> No. But of course that is completely beside the
point of this whole
>> discussion, which you are trying to steer away from
the real issue, which
>> you haven't adressed in a single post.
>
>It's not.
>
>Lots of extensions which perform operations in the page
add a menu item 
>to the menu bar. You are saying that we shouldn't make
it possible to 
>view the menu bar in popup windows.

No. I'm saying that it is a hacky workaround. It is a
definitely a better
solution than the current situation, but it could obviously
be improved.

>Therefore, you are saying that all these extensions
should also add a 
>context menu item in case they need to be used on such
pages.

You have serious reading problems, Gerv. When I learned
English "No" was
a negation. Has this changed?

>> There are valid use cases for the inclusion of a
print option on the
>> context menu, 
>
>Are they stronger than the use case for a Find option?

Yes. "Read" the bug with all the examples.

>>  |"One can't consider context menu additions
in isolation; that's what 
>>  |leads to the 29-item context menus we had (have?)
in Seamonkey."
>> 
>> is brought up again.
>
>Er, that's because it's a reasonable point.

No, it's complete bullshit. And I explained to you why the
linkage to the
Seamonkey situation is wrong a few posts earlier. If you
would actually
read my postings, you would know that.

>All of the things I listed have the potential to be
required on any page. 
>Therefore, if we considered them all in isolation, we'd
add context menu 
>items for all of them.

Usability design means making tradeoffs by identifying the
elements which
are *really* important to the user and to weed out all the
stuff which is
only mildly interesting or even distracting to the user. 

That's what this discussion should be about: Discussing the
potential
benefits and drawbacks of a print contextmenu-item and not
holding the
26th strawman discussion about the Seamonkey contextmenu
disaster.

Simon
-- 
Sunbird/Lightning Website Maintainer:
http://www.m
ozilla.org/projects/calendar
Sunbird/Calendar blog: http://weblog
s.mozillazine.org/calendar
_______________________________________________
dev-apps-firefox mailing list
dev-apps-firefoxlists.mozilla.org
h
ttps://lists.mozilla.org/listinfo/dev-apps-firefox

Simon Paquet wrote:

> Usability design means making tradeoffs by identifying
the elements which
> are *really* important to the user and to weed out all
the stuff which is
> only mildly interesting or even distracting to the
user.

I've read the bug and probably all of the forum posts, the
few blog 
posts, and the newsgroup threads. I've yet to see any
compelling data 
that says this is a *really* important issue for any
significant number 
of users.  My reading suggests that this issue falls much
closer to the 
"mildly interesting" category.

- A
_______________________________________________
dev-apps-firefox mailing list
dev-apps-firefoxlists.mozilla.org
h
ttps://lists.mozilla.org/listinfo/dev-apps-firefox

Simon Paquet wrote:
> And on the seventh day Gervase Markham spoke:
>> Rubbish. We allow it in lots of places. "Use
own fonts and colours". 
>> "Set Text Size".
> 
> What in "major usability concerns" did you
not understand?

For some users, "Use own fonts and colours" and
"Set Text Size" are 
major usability concerns. You need to hang out with the
accessibility 
folks a little bit.

>> The entire point of Greasemonkey is to mess around
with 
>> developed content that is not your own.
> 
> Greasemonkey is an extension. And there are valid
reasons why it is not
> included by default.

If there were a way we could do it without the implicit
security 
problems with untrusted code, believe me, it would be in
there like a 
shot. Opera includes their version by default.

> You have serious reading problems, Gerv. When I learned
English "No" was
> a negation. Has this changed?

Then how am I supposed to access these extensions on pages
where I can't 
get at the menu bar?

> No, it's complete bullshit. And I explained to you why
the linkage to the
> Seamonkey situation is wrong a few posts earlier. If
you would actually
> read my postings, you would know that.

Clearly I'm not reading your postings. That's how I'm not
responding to 
them, point by point.

Just because someone disagrees with you doesn't mean he is
either stupid 
or ignoring you.

> That's what this discussion should be about: Discussing
the potential
> benefits and drawbacks of a print contextmenu-item and
not holding the
> 26th strawman discussion about the Seamonkey
contextmenu disaster.

No, the discussion should be about the general issue. Popup
windows 
without a menu bar remove function a user might want. How do
we fix 
that, bearing in mind that we can't know exactly what the
function is 
because of extensions?

Note that a solution to this problem may not involve the
context menu at 
all. It might involve making the menu bar compulsory; it
might involve 
adding a "Show Menu Bar" button to the top right
corner.

Gerv
_______________________________________________
dev-apps-firefox mailing list
dev-apps-firefoxlists.mozilla.org
h
ttps://lists.mozilla.org/listinfo/dev-apps-firefox