Proximity event is occurred normally even if value is less than min or more then max. Therefore we need to add checking the range of proximity value.
Created attachment 189271 [details] Patch
Comment on attachment 189271 [details] Patch I wonder whether this should be done in WebCore. Why not handle this in client side and just assert the range here?
(In reply to comment #2) > (From update of attachment 189271 [details]) > I wonder whether this should be done in WebCore. Why not handle this in client side and just assert the range here? As you said, client can check this. IMHO, we need to add a minimal defense in the WebCore, but I'm not strongly sure about this. Could I get your opinion about this?
(In reply to comment #3) > (In reply to comment #2) > > (From update of attachment 189271 [details] [details]) > > I wonder whether this should be done in WebCore. Why not handle this in client side and just assert the range here? > > As you said, client can check this. > IMHO, we need to add a minimal defense in the WebCore, but I'm not strongly sure about this. Could I get your opinion about this? Just add an assertion here and a guard on caller side?
Add ASSERT to didChangeDeviceProximity function to check range of value. In addition, fix some wrong layout test cases.
Created attachment 189903 [details] Patch
Comment on attachment 189903 [details] Patch Clearing flags on attachment: 189903 Committed r143882: <http://trac.webkit.org/changeset/143882>
All reviewed patches have been landed. Closing bug.