3
It is correct to put the attribute href
in a mark other than a
.
Example:
<ul>
<li href="#page1">Page1</li>
<li href="#page2">Page2</li>
<li href="#page3">Page3</li>
<li href="http://www.google.fr">Page3</li>
</ul>
Apparently it worked in my case, but that’s correct?
What do you call "worked"? Here it is simply ignored. It may be that your browser does something out of the standard and uses href for something, but it is "invention" of the manufacturer. .
– Bacco
In the example of my post clearly does not work, but integrating in my app is working put. What problems can I find in the future ?
– PululuK
The problem you already found, which is "work". It’s not supposed to work, if "works" there is something wrong with the APP right now, and not in the future. When something works when it shouldn’t, it’s a sign of something wrong too.
– Bacco
kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk !!!
– PululuK
Seriously, I’m not "joking," no, it would be absurd to expect something that shouldn’t be like this, because the result is unpredictable. It can be a coincidence and only work in rare cases. It can be a JS that is using the links, and not the webview or browser. You can’t trust this at all.
– Bacco
The exception to this would be you find in the official documentation of the platform something like this: "Support for href has been extended in all elements ..." etc, so it would be official. Otherwise, it is better not to risk.
– Bacco
I fully understand your cautionary tendencies, and thanks !
– PululuK