101225 2012-11-05 08:38:40 -0800 Enable automated mouse cursor tests on more ports 2022-07-13 11:42:20 -0700 1 1 1 Unclassified WebKit CSS 528+ (Nightly build) Unspecified Unspecified NEW DoNotImportToRadar P2 Normal --- 100550 1 rbyers webkit-unassigned bfulgham mifenton mmacleod rbyers tonikitoo oldest_to_newest 758570 0 rbyers 2012-11-05 08:38:40 -0800 In bug 100550 some automated tests were added (fast/events/mouse-cursor.html) for testing mouse cursor behavior, and more tests will follow using the same infrastructure. These tests rely on a 'testRunner.getCurrentCursorInfo' API which needs to be added to each port that wants to use these tests (currently only chromium has it). This bug tracks adding the getCurrentCursorInfo API to the other ports and unskipping the mouse-cursor tests on that port (port-specific bugs can be filed for each port as desired). 762075 1 rbyers 2012-11-08 12:40:41 -0800 I changed the test infrastructure work on all ports that define USE(LAZY_NATIVE_CURSOR) - i.e. Mac, Win, GTK, QT and EFL. Chromium will get this soon in bug 101501. I think (but I'm not sure) that leaves only BLACKBERRY and WX, neither of which appear to have TestExpectations files in the tree. Antonio, any idea if blackberry will want this, and if I should be listing the test as failing on blackberry somewhere? Malcolm, looks like you recently did cursor work for WX - what about that port? 762920 2 tonikitoo 2012-11-09 05:57:59 -0800 m(In reply to comment #1) > I changed the test infrastructure work on all ports that define USE(LAZY_NATIVE_CURSOR) - i.e. Mac, Win, GTK, QT and EFL. > > Chromium will get this soon in bug 101501. > > I think (but I'm not sure) that leaves only BLACKBERRY and WX, neither of which appear to have TestExpectations files in the tree. > > Antonio, any idea if blackberry will want this, and if I should be listing the test as failing on blackberry somewhere? > > Malcolm, looks like you recently did cursor work for WX - what about that port? mike?