Skip to content

Commit

Permalink
v0.0.10
Browse files Browse the repository at this point in the history
  • Loading branch information
jgerigmeyer committed Mar 3, 2023
1 parent 09925a8 commit 761a994
Show file tree
Hide file tree
Showing 4 changed files with 10 additions and 10 deletions.
4 changes: 2 additions & 2 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
# Popover Attribute Polyfill Changelog

## UNRELEASED
## 0.0.10: 2023-03-03

- 🏠 INTERNAL: Upgrade dependencies
- 🚀 NEW: Add support for `aria-expanded` on invokers --
[#77](https://github.com/oddbird/popover-polyfill/pull/77)
- 🏠 INTERNAL: Upgrade dependencies

## 0.0.9: 2023-02-03

Expand Down
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,7 +85,7 @@ attributes to the HTMLElement class.

## Caveats

This polyfill is not a perfect replacement for the native behavior, there are
This polyfill is not a perfect replacement for the native behavior; there are
some caveats which will need accommodations:

- Native `popover` has an `:open` and `:closed` pseudo selector state. This is
Expand All @@ -98,7 +98,7 @@ some caveats which will need accommodations:
- Using native `:open` in CSS that does not support native `popover` results
in an invalid selector, and so the entire declaration is thrown away. This
is important because if you intend to style a popover using `.\:open` it
will need to be a separate declaration. e.g.
will need to be a separate declaration. For example,
`[popover]:open, [popover].\:open` will not work.

- Native `popover` elements use the `:top-layer` pseudo element which gets
Expand All @@ -108,7 +108,7 @@ some caveats which will need accommodations:
`overflow:` or `position:` CSS, then there will be visual differences between
the polyfill and the native behavior.

- Native _invokers_ (that is: buttons or inputs using the `popoverHideTarget`,
- Native _invokers_ (that is, buttons or inputs using the `popoverHideTarget`,
`popoverShowTarget`, or `popoverToggleTarget` attributes) on `popover=auto`
will render in the accessibility tree as elements with `expanded`. The only
way to do this in the polyfill is setting the `aria-expanded` attribute on
Expand Down
6 changes: 3 additions & 3 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@oddbird/popover-polyfill",
"version": "0.0.9",
"version": "0.0.10",
"description": "Popover Attribute Polyfill",
"license": "BSD-3-Clause",
"publishConfig": {
Expand Down Expand Up @@ -87,7 +87,7 @@
},
"devDependencies": {
"@playwright/test": "^1.31.2",
"@types/node": "^18.14.6",
"@types/node": "*",
"@typescript-eslint/eslint-plugin": "^5.54.0",
"@typescript-eslint/parser": "^5.54.0",
"esbuild": "^0.17.10",
Expand Down

0 comments on commit 761a994

Please sign in to comment.