destyle.css - npm Package Compare versions

Comparing version 1.0.7 to 1.0.8

package.json

		{
		"name": "destyle.css",
		"version": "1.0.7",
		"version": "1.0.8",
		"description": "Opinionated reset stylesheet that provides a clean styling slate for your project.",
		@@ -5,0 +5,0 @@ "main": "destyle.css",

Readme.md

		@@ -114,3 +114,3 @@ # destyle.css

		`button` tags have a lot of default styles that can make them cumbersome to use from a styling perspective, especially if they should look like plain things or need to wrap some other content, but `button` tags are the recommended elements to use as click targets for user interactions. Falling back to using `<a href="#">` even with `role="button"` is [not recomended](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/button_role) from a accessibility standpoint as Screenreaders will recognize `button`s as interactive elements by default and treat them accordingly. `a` should be used when there is the need to link to a page via `href`.
		`button` tags have a lot of default styles that can make them cumbersome to use from a styling perspective, especially if they should look like plain things or need to wrap some other content, but `button` tags are the recommended elements to use as click targets for user interactions. Falling back to using `<a href="#">` even with `role="button"` is [not recomended](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/button_role) from an accessibility standpoint as Screenreaders will recognize `button`s as interactive elements by default and treat them accordingly. `a` should be used when there is the need to link to a page via `href`.

		@@ -117,0 +117,0 @@ destyle.css resets buttons completely to make them usable as any other element <small>* see note [below](#caveats)</small>.

destyle.css

Sorry, the diff of this file is not supported yet

New alerts