Summary: | Enable automated mouse cursor tests on more ports | ||
---|---|---|---|
Product: | WebKit | Reporter: | Rick Byers <rbyers> |
Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW --- | ||
Severity: | Normal | CC: | bfulgham, mifenton, mmacleod, rbyers, tonikitoo |
Priority: | P2 | Keywords: | DoNotImportToRadar |
Version: | 528+ (Nightly build) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Bug Depends on: | 100550 | ||
Bug Blocks: |
Description
Rick Byers
2012-11-05 08:38:40 PST
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? 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? |