Ç¥ÁØÈ­ Âü¿©¾È³»

TTAÀÇ Ç¥ÁØÇöȲ

Ȩ > Ç¥ÁØÈ­ °³¿ä > TTAÀÇ Ç¥ÁØÇöȲ

Ç¥ÁعøÈ£ TTAE.OT-10.0387 ±¸Ç¥ÁعøÈ£
Á¦°³Á¤ÀÏ 2015-12-16 ÃÑÆäÀÌÁö 36
ÇѱÛÇ¥Áظí À¥¿¡¼­ÀÇ Æ÷ÀÎÅÍ À̺¥Æ® ÀÎÅÍÆäÀ̽º
¿µ¹®Ç¥Áظí Pointer Events
Çѱ۳»¿ë¿ä¾à ÀϹÝÀûÀ¸·Î ÀüÅëÀûÀÎ À¥ ÄÁÅÙÃ÷µéÀº ¸¶¿ì½º ÀÔ·Â ÀåÄ¡¸¦ ±â¹ÝÀ¸·Î Á¢±ÙÇÏ´Â ¹æ½ÄÀ¸·Î ¼³°èµÇ¾î ÀÖ´Ù. ±×·¯³ª ÃÖ±Ù ½º¸¶Æ®Æù°ú ÅÂºí¸´ µî »ç¿ëÀÚ ´Ü¸» À¯ÇüµéÀÌ ´Ù¾çÇØÁö¸é¼­ Æ÷ÀÎÆà ÀÔ·Â ÀåÄ¡ ¶ÇÇÑ Ææ, ÅÍÄ¡ ½ºÅ©¸° µî°ú °°ÀÌ ´Ù¾çÇØÁö°í ÀÖ°í, »õ·Î¿î Æ÷ÀÎÆà ÀÔ·Â ÀåÄ¡¸¦ È°¿ëÇÏ´Â »ç·Êµéµµ °è¼Ó ¸¹¾ÆÁö°í ÀÖ´Ù. ¶ÇÇÑ ´Ù¾çÇÑ Æ÷ÀÎÆà ÀÔ·Â ÀåÄ¡¸¦ Áö¿øÇϱâ À§ÇØ º¹ÀâÇÑ ±¸ÇöµéÀ» °è¼Ó ÇØ¾ß ÇÏ´Â »óȲÀº ¿©·¯ °¡Áö »óÈ£ ȣȯ¼ºÀÇ ¹®Á¦¸¦ ¹ß»ý½ÃÅ°°Ô µÇ¾ú´Ù. ÀÌ¿¡ º» Ç¥ÁØ¿¡¼­´Â Æ÷ÀÎÆà ÀÔ·Â Çϵå¿þ¾î¿¡ Á߸³ÀûÀ¸·Î Ãß»óÈ­µÈ Æ÷ÀÎÆà ÀÔ·ÂÀ» ó¸®ÇÒ ¼ö ÀÖµµ·Ï Çϱâ À§ÇÑ Æ÷ÀÎÅÍ À̺¥Æ®¸¦ Á¤ÀÇÇÑ´Ù.
¿µ¹®³»¿ë¿ä¾à Today, most [HTML5] content is used with and/or designed for mouse input. Those that handle input in a custom manner typically code to [DOM-LEVEL-3-EVENTS] Mouse Events. Newer computing devices today, however, incorporate other forms of input, including touchscreens, pen input, etc. Event types have been proposed for handling each of these forms of input individually. However, that approach often incurs unnecessary duplication of logic and event handling overhead when adding support for a new input type. This often creates a compatibility problem when content is written with only one device type in mind. Additionally, for compatibility with existing mouse-based content, most user agents fire Mouse Events for all input types. This makes it ambiguous whether a Mouse Event represents an actual mouse device or is being produced from another input type for compatibility, which makes it hard to code to both device types simultaneously.
To reduce the cost of coding to multiple input types and also to help with the above described ambiguity with Mouse Events, this specifications defines a more abstract form of input, called a pointer. A pointer can be any point of contact on the screen made by a mouse cursor, pen, touch (including multi-touch), or other pointing input device. This model makes it easier to write sites and applications that work well no matter what hardware the user has. For scenarios when device-specific handling is desired, this specification also defines properties for inspecting the device type which produced the event. The primary goal is to provide a single set of events and interfaces that allow for easier authoring for cross-device pointer input while still allowing for device-specific handling only when necessary for an augmented experience.
±¹Á¦Ç¥ÁØ
°ü·ÃÆÄÀÏ TTAE.OT-10.0387.pdf TTAE.OT-10.0387.pdf            

ÀÌÀü
½Ã¼Ò·¯½º °³¹ß Áöħ
´ÙÀ½
±â¾÷ ÇÁ·ÎÆÄÀÏ Ç¥Çö ¹æ¹ý Ç¥ÁØ