Kyle Kovacs
Kyle Kovacs
It looks to me like the problem stems from a `` element inside a non-default tab of the `Tabs` container widget. [This is the page](https://docusaurus.io/docs/deployment#triggering-deployment-with-github-actions) that has the issue. This...
Here are my suggestions: ## Long-Term An actual fix for this would involve modifying the code to artificially click on the first tab, copy its contents into the DOM, then...
@karl-cardenas-coding I haven't looked into the source code of this repo much, but assuming the `excludeSelector` is using something like [`document.querySelectorAll`](https://developer.mozilla.org/en-US/docs/Web/API/Document/querySelectorAll), the selector can be any [CSS selector](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_selectors). So if...
I don't know what I did, oops. Did not mean to close the PR.
@lewis6991 @justinmk Ongoing discussion about a possible `Search` event here: https://github.com/vim/vim/issues/17791
Yep, looks like it's OK now.
@alerque It's kind of a hard sell when [60%+ of the world uses Google Chrome](https://en.wikipedia.org/wiki/Usage_share_of_web_browsers) and only 6-7% Firefox and Edge combined. Shame about the policy change though. And I...
> The extension still works Not anymore after today's update :(
In my browser, activating the extension just turns the input field into a black box unfortunately.
I removed the extension, cloned the repo in WSL, ran the setup steps, then coped the `target/chrome` folder into my Windows file system, then used "Load unpacked." Chrome still thinks...