Design Fault: Document Object Model (DOM) Level 3 Events Specification

Hi,
in section "1.6.2. Mouse event types" is still a design fault:
  button of type unsigned short, readonly
    During mouse events caused by the depression or release of a mouse
    button, [...]

Problem:
If a mouse button depressed inside the document area but released
outside and mouse reenter the document area, there is no chance
to indicate, that no mouse button is depressed.

There is a common (failing) use case for drag & drop:
 - A drag action has been started inside the document area
   and the drag element is carry along the mouse pointer
 - Mouse pointer has been moved outside the document area
   and the drag element stand still on last mouse move/out position
 - Mouse button has been released
 - Mouse pointer has been moved inside the document area
   and the drag element still carry along the mouse pointer,
   although no mouse button depressed.

Solution:
 - button attribute should be updated during *ALL* mouse events
 - button attribute should be implemented as a bit mask (respectively
   for another attribute should be provide, to

I know, there are a lot of stalled discussions about this stuff.
Please keep in mind: A Web-Applications needs a well-performing
drag functionality, and currently only MS Internet Explorer provide it!


salute
Thomas

--
Thomas Fischer
Software Engineer

NOKIA Software & Services
Context, Advertising, and Emerging Markets

Received on Friday, 25 July 2008 13:01:07 UTC