needs fuzzing, mobile fuzzing research needed
Do you want the DOM fuzzer run on mobile devices that use accelerated layers? Or something else? How different is this from setting layers.acceleration.force-enabled on desktop OSes? Which device and OS do you recommend starting with? (Ideally something that's relatively easy to automate and debug, and which passes reftests and mochitests.)
Assignee: jruderman → general
OS: Mac OS X → All
Hardware: x86 → All
(In reply to Jesse Ruderman from comment #1) > Do you want the DOM fuzzer run on mobile devices that use accelerated > layers? Or something else? Yes I think that was the intent when this was assigned. This task was assigned to you per the wiki page, so I had assigned this bug to you as a place to track the work so we can close out that work. > How different is this from setting layers.acceleration.force-enabled on > desktop OSes? I don't know, cc:jpr as he is listed on wiki as responsible individual for input. > Which device and OS do you recommend starting with? (Ideally something > that's relatively easy to automate and debug, and which passes reftests and > mochitests.) Again I don't know the answer to this question. I think this needs to be answered by the fuzzers in general and by the product team. assigning back to you per the wiki note, if this is not correct please work with dveditz for reassignment.
Assignee: general → jruderman
Status: NEW → ASSIGNED
QA Contact: security-assurance
](In reply to Jesse Ruderman from comment #1) > How different is this from setting layers.acceleration.force-enabled on > desktop OSes? That pref wont give you what you want. The closest thing on desktop is 'layers.offmainthreadcomposition.enabled' on mac only. This doesn't run the same way on Android because there we support async scrolling, different widget binding and integrate with the Java frontend.
I tried randomizing layers.offmainthreadcomposition.enabled and quickly ran into some serious bugs, bug 736219 and bug 717925. It would be nice if you fixed those first :)
Risk/Priority Ranking Exercise https://wiki.mozilla.org/Security/RiskRatings Priority: N/A Operational: 1 - Minor User: 1 - Minor Privacy: 0 - N/A Engineering: 2 - Normal Reputational: 1 - Minor Priority Score: 0
You need to log in before you can comment on or make changes to this bug.