Repository navigation
Page selectors #24
Description
This GitHub issue is for collecting web developer signals for Page selectors.
The :first, :left, and :right pseudo-classes select pages based on their position in sequence after pagination.
Browser support
- Chrome 18 (Mar 28, 2012)
- Chrome Android 18 (Jun 27, 2012)
- Edge 12 (Jul 29, 2015)
- Firefox: not supported
- Firefox for Android: not supported
- Safari 6 (Jul 25, 2012)
- Safari on iOS 6 (Sep 10, 2012)
Give us feedback
If you're pressed for time, but you want this feature to be available in all browsers, please give this issue a thumbs up 👍 reaction.
However, a much better guide for us is to know how you'd use this feature, and what you're having to do in the meantime. This helps us judge the priority versus other features.
Copy the template below in a comment, and add the details that matter to you.
## What I want to do with this feature
<!-- Add your specific use-cases, even if they seem obvious to you. -->
## What I'm having to do in the meantime
<!--
Are you having to use another feature instead, a polyfill, or is it blocking you completely?
Why are the alternatives worse than using this feature?
-->All comments are expected to adhere to the Code of Conduct.
Learn more
You can learn more about this feature here:
Activity
tif-calin commentedon Dec 27, 2025
Multiple times in my professional career I've worked on commercial products that involve rendering an editable/interactive HTML preview of some pages that then need to be printed. The inconsistency between the way browsers handle print media and print-related CSS has been a massive painpoint. It is not uncommon for teams to build microservices that just spin up a Selenium instance, prints the page, and then sends that back to the front-end just so that when users click "Print" they get a consistent output
I'm desperate for any attention to print media