<feed xmlns='http://www.w3.org/2005/Atom'>
<title>Legibility/Makefile, branch master</title>
<subtitle>A WebExtension that lets you override the CSS of any website</subtitle>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/Legibility/'/>
<entry>
<title>Add a way to get rid of the reload keyboard shortcut for Chrome</title>
<updated>2021-09-19T20:27:14+00:00</updated>
<author>
<name>Teddy Wing</name>
</author>
<published>2021-09-19T20:27:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/Legibility/commit/?id=ee4954a4f31702495d6ff54ace8c5e06c0eb4c8f'/>
<id>ee4954a4f31702495d6ff54ace8c5e06c0eb4c8f</id>
<content type='text'>
The keyboard shortcut for reloading the extension causes the extension
to fail to load in Chrome. That happens because the default shortcut
uses the Control and Option modifiers together:

&gt; Key combinations that involve Ctrl+Alt are not permitted in order to
&gt; avoid conflicts with the AltGr key.

https://developer.chrome.com/docs/extensions/reference/commands/#key-combinations

Provide a way to remove the keyboard shortcuts from the manifest for
Chrome. The shortcuts aren't necessary in Chrome, as new CSS files and
changes to existing ones are automatically recognised without having to
reload the extension. On Firefox, the extension must be manually
reloaded in order for CSS changes to take effect.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The keyboard shortcut for reloading the extension causes the extension
to fail to load in Chrome. That happens because the default shortcut
uses the Control and Option modifiers together:

&gt; Key combinations that involve Ctrl+Alt are not permitted in order to
&gt; avoid conflicts with the AltGr key.

https://developer.chrome.com/docs/extensions/reference/commands/#key-combinations

Provide a way to remove the keyboard shortcuts from the manifest for
Chrome. The shortcuts aren't necessary in Chrome, as new CSS files and
changes to existing ones are automatically recognised without having to
reload the extension. On Firefox, the extension must be manually
reloaded in order for CSS changes to take effect.
</pre>
</div>
</content>
</entry>
</feed>
