* Only fixup margins in `p` tags when inside a list item
The intent of these selectors are to only target `p` tags but we are targeting `*:first-child` and `*:last-child`. This has a side effect of causing `<br>` elements inside the list item to gain a margin _only in Firefox_. Other browsers treat the `<br>` element as properly inline and as such don’t apply margins but FF does not seem to.
* Update changelog
* Add `prose-kbd` element modifier
Add selector, update readme and tests.
* Change order of `kbd` modifier
---------
Co-authored-by: Jonathan Reinink <[email protected]>
* Add support for the `<kbd>` element
* Make border variable name plural
* Add size-modifier specific padding
* Tweak property order
* Update design
* Tweak padding and font size
* Update changelog
* Style `tfoot td` same as `tbody td`
**Problem**
If you've got a CMS that generates a `tfoot` tag for table footers, the `td`s contained in it are not aligned with the `td`s in `tbody`.
**Solution**
Style `tfoot td` the same as `tbody td`.
* Add border to `tfoot`
* Update `tfoot` styles for all sizes
* Adjust tailwind.config.js to match v3 (drop purge: entry)
* Adjust tests to tw3 non-alpha output
* run prettier on test file
* rename `twVariables` to `defaults`
This is more inline with what we do in the tailwindcss codebase itself
* embed the `${defaults}` directly
Co-authored-by: Ingo Struck (git commits) <[email protected]>
* Start scaffolding out components/modifiers
* WIP
* Updated pre-code and pre-bg colors
* WIP
* Add some notes
* WIP
* handle nested objects, e.g.: `@media`
* WIP
* simplify invert mode
* simplify base styles
* add `prose-XXX` variants
* update demo pages
* bump tailwind version
* mark insiders as a valid peer dependency
* bump next
* use package-lock.json file
* cleanup
* add more variants
* rename `rules` to `hr`
* update test snapshots
We probably want to look at other testing mechanisms here.
* cleanup index file
* improve API
* Simplify variants, add more element variants
* Refactor to use ::marker
* Tweak marker positions to work better across multiple browsers
* Simplify testing strategy
Co-authored-by: sschoger <[email protected]>
Co-authored-by: Robin Malfait <[email protected]>
* Use :where to reduce specificity
* Update index.js
* Handle before/after with :where
This is a fairly naive solution and could/should be made more robust to handle other pseudo-elements like ::first-letter, ::first-line, etc. but I'm inclined to just roll with this until someone actually opens an issue because they needed support for those.
* Only wrap selectors with :where(), not property names
* Add new `target` plugin option to enable/disable the use of `:where()` selectors
Co-Authored-By: Adam Wathan <[email protected]>
Co-authored-by: Jonathan Reinink <[email protected]>
* Use the implicit `list-item` counter
Signed-off-by: Peter Neupauer <[email protected]>
* update tests
Co-authored-by: Peter Neupauer <[email protected]>
