<a>
tag it will be clicked but on <div>
element will do nothing.therfore :foucs
psd-class will have no impact on a tag with accesskey
attribute value.finally incase of two tags with the same accesskey
attribute value the browser will show small tab at the bottom with the name of the last element accessed via(alt+shift+key
) on windows os then i need to press Enter
to choose wich to be used-this was tested with <a>
tag.true false & inherit
.this attribute is not boolean however.it is enumurated instead,that is inorder for tag element to be editable true
value need to be assigned.false
will stop the element from being editable.inherit when tested showed nill effect.speaking of making element tag editable,conteneditable
attribute mostly used on text to be modified by users,but it also work on images-can be resized.al that said with one problem the image tag element needs to be inside a container-no explination why and set the attribute of that image container to be editable.now let's speak some inheritance.if a tag element is not set to be editable it will inherit this attribute if it's parent is. direction & unicode-bidi
incase of css is not activated.it takes values rtl ltr
and auto
.always set it to auto
if it is impossible to know what language to be used(user input) the browser will decide depending on user input.important note is that changing the directionality of element will change the direction of rendering and document flow inside it accordingly.keep in mind that using this attribute will not cause the text characters to be flipped.example if text is in english and dir
is rtl
it won't cause it to be like this: hsilgne.this only happens when used with element <bdo>
.display
overrides the presence of hidden
attribute.lang
attribute need to be defined along with spellcheck
attribute.when specified on non-editable tags it will have no effect since browsers mainly do not check for spelling erorrs however it has full effect on editable elements-elements that have contenteditable
set on.it makes sense since only editable elements are exposed to spelling errors-when a user insert new text.hidden
attribute should be used instead-or css display
is even better since it overrides hidden
.tabindex
attribute takes integer number as a value:
tabindex="0"
the attribute changes the state of the element to be foucsable within the normal source order of the document.tabindex="-1"
the attribute changes the state of the element to be foucasble along with the use of script-only a script can take care of making it visually foucsable.keyboard will not.foucsed
on the screen and users are interacting with it.tabindex="1"
or any positive integer-read this