You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whilst taking a look at #211 I noticed a related issue when using the polyfill: Safari ignores the onclose handler attribute.
As a result the following important application functions correctly in Chrome, and in Firefox (with both native and polyfilled dialogs), but not in polyfill'd Safari:
Now, for contextual reasons the telling of which is beyond the scope of this bug report, this fragment could not be easily changed, nor could it be extracted to a good old-fashioned addEventListener. Imagine my dismay at such a critical utility being therefore unavailable to a reasonable proportion of users.
Instead, I hacked in support, by forcing Safari to compile the handler string in the approved manner via an otherwise unused handler attribute that it does choose to honour:
and this works, and works particularly well by leaning on the otherwise inaccessible browser internals implementing the Event Handler Content Attribute Change Steps, and it works across the browsers I personally have to shepherd along; however, I'm unsure whether there's a less depraved solution, and of course devotees of the <summary>/<details> combo will have stern things to say about my abuse of ontoggle, and polyfill authors of my flagrant disregard for backwards compatibility.
The text was updated successfully, but these errors were encountered:
Whilst taking a look at #211 I noticed a related issue when using the polyfill: Safari ignores the
onclose
handler attribute.As a result the following important application functions correctly in Chrome, and in Firefox (with both native and polyfilled dialogs), but not in polyfill'd Safari:
Now, for contextual reasons the telling of which is beyond the scope of this bug report, this fragment could not be easily changed, nor could it be extracted to a good old-fashioned
addEventListener
. Imagine my dismay at such a critical utility being therefore unavailable to a reasonable proportion of users.Instead, I hacked in support, by forcing Safari to compile the handler string in the approved manner via an otherwise unused handler attribute that it does choose to honour:
and this works, and works particularly well by leaning on the otherwise inaccessible browser internals implementing the Event Handler Content Attribute Change Steps, and it works across the browsers I personally have to shepherd along; however, I'm unsure whether there's a less depraved solution, and of course devotees of the
<summary>/<details>
combo will have stern things to say about my abuse ofontoggle
, and polyfill authors of my flagrant disregard for backwards compatibility.The text was updated successfully, but these errors were encountered: