Skip to content
This repository has been archived by the owner on Feb 11, 2021. It is now read-only.

Commit

Permalink
Add navigator.maxTouchPoints to current list of limitations
Browse files Browse the repository at this point in the history 
Ref gh-332
Closes gh-334
  • Loading branch information
@patrickhlauke @scottgonzalez
patrickhlauke authored and scottgonzalez committed Mar 3, 2017
1 parent 3a43f69 commit d1aa08d
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -100,6 +100,10 @@ Due to the difficult nature of polyfilling new CSS properties, this library will

Touches will not generate events unless inside of an area that has a valid `touch-action` attribute defined. This is to maintain composition scrolling optimizations where possible.

## navigator.maxTouchPoints

As the information necessary to populate [`navigator.maxTouchPoints`](https://www.w3.org/TR/pointerevents/#extensions-to-the-navigator-interface) is not available in browsers that do not natively implement pointer events, PEP does not currently polyfill this extension to the `navigator` interface.

### Browser Compatibility

PEP should work on IE 10+ and the latest versions of Chrome, Safari, Firefox, and Opera. In any [browser implementing pointer events natively](http://caniuse.com/#feat=pointer) (detected by checking for `window.PointerEvent`), PEP won't do anything.
Expand Down

0 comments on commit d1aa08d

Please sign in to comment.