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

TTAÀÇ Ç¥ÁØÇöȲ

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

Ç¥ÁعøÈ£ TTAE.OT-10.0387/R1 ±¸Ç¥ÁعøÈ£
Á¦°³Á¤ÀÏ 2019-12-11 ÃÑÆäÀÌÁö 61
ÇѱÛÇ¥Áظí À¥¿¡¼­ÀÇ Æ÷ÀÎÅÍ À̺¥Æ® ÀÎÅÍÆäÀ̽º-·¹º§ 2
¿µ¹®Ç¥Áظí Pointer Events Level 2
Çѱ۳»¿ë¿ä¾à º» Ç¥ÁØÀº ¸¶¿ì½º ÀÔ·Â ÀåÄ¡ ±â¹ÝÀ¸·Î À¥ ÄÜÅÙÃ÷¿¡ Á¢±ÙÇÏ´Â ¹æ½Ä°ú´Â º°µµ·Î ½º¸¶Æ®Æù°ú ÅÂºí¸´ µî ´Ü¸» À¯Çü¿¡ ¸Âµµ·Ï ´Ù¾çÇÑ Æ÷ÀÎÅÍ ÀÔ·Â ÀåÄ¡(Ææ, ÅÍÄ¡½ºÅ©¸° µî)¸¦ °í·ÁÇÏ¿© ¸¶¿ì½º ±â¹Ý ÄÜÅÙÃ÷¿ÍÀÇ È£È¯¼ºÀ» À§ÇÑ ´Ù¸¥ Æ÷ÀÎÅÍ ÀåÄ¡ ŸÀÔµé°ú ¸¶¿ì½º À̺¥Æ®ÀÇ ¿¬°á ¹æ¹ý¿¡ ´ëÇؼ­ ±â¼úÇÑ´Ù.
¿µ¹®³»¿ë¿ä¾à The standard 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. Today, most [HTML5] content is used with and/or designed for mouse input. Those that handle input in a custom manner typically code to 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.
±¹Á¦Ç¥ÁØ
°ü·ÃÆÄÀÏ TTAE.OT-10.0387_R1.pdf TTAE.OT-10.0387_R1.pdf            

ÀÌÀü
IMT-2000 3GPP - UTRA Áß°è±â; ¹«¼± Àü¼Û°ú ¼ö½Å (R8)
´ÙÀ½
IMT-2000 3GPP - ±âÁö±¹ EMC (R8)