W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > April 2009

[Bug 6606] generic 3rd-party <mark>, Smart Tags, and Activities prevention

From: <bugzilla@wiggum.w3.org>
Date: Sat, 04 Apr 2009 22:42:58 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1LqEZm-0002oQ-83@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6606


Nick Levinson <Nick_Levinson@yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Platform|PC                          |All




--- Comment #3 from Nick Levinson <Nick_Levinson@yahoo.com>  2009-04-04 22:42:58 ---
A partial solution may have been instituted, first by Microsoft applicable to
Internet Explorer 5 and later and then by HTML 5: the attribute
oncontextmenu="return false" added to the body element or any, maybe every,
other element.

Credit goes to a Usenet poster
(<http://groups.google.com/group/microsoft.public.internetexplorer.general/browse_thread/thread/cf6f11a21ebb0a04>).
I did suggest at a website forum on Web authoring the possibility of testing to
verify that this works, but haven't heard back. (I don't have a platform for
IE8.)

What this is supposed to do is block the context menu. If IE8 Accelerators are
only in the context menu and not in any other menus, fine. If they're also
elsewhere, then the attribute is not good enough. Since the feature is in IE8
Beta, possibly MS will use the final release to put Accelerators into a regular
menu in addition, thus defeating the attribute value. Also, if the context menu
has any other command that's not an Accelerator but also is not in the menubar
menus, then this attribute value may be excessive. And if IE8 has or will have
two context menus, one for Accelerators and the other for other commands, the
Accelerators context menu may not respond to this attribute value.

It also doesn't meet the legal need for an all-platform all-UA all-tool method,
so that anyone claiming compliance has to offer website authors a way to block
any similar technology.

If left to a proprietor, say, Microsoft, I'm concerned they'll want to punish
us, like they tried to do to people who wanted to use non-MS software with Win,
in this case by disabling much more than just Accelerators by making their
browser noncompliant apart from Accelerator absence.

So we still need a brand-independent method.

Thank you.

-- 
Nick


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Saturday, 4 April 2009 22:43:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:00:53 UTC