I'm trying to help my girlfriend with eshop, so I was trying to repair all the errors on her prestashop installation. Unfortunately, I'm stuck here too because I can't repair last one. It's about target property in anchors from one module. This is the page:
ciapkydede.sk
and here is W3C validation:
http://validator.w3.org/check?uri=ciapkydede.sk&charset=%28detect+automatically%29&doctype=Inline&group=0
Please, can someone help me solve this problem or at least give me some direction where to look? I'll be even thankful for advice about debugging.
The target attribute is not valid in XTHML 1.1
You can remove the target="_self" attribute since the default value for target is _self or you can continue to use it and ignore the validator error since it is supported in all browsers and is valid in HTML5.
Related
I can't figure out what's going on, here is my HTML. The validator gives me errors, but I'm completely new to this so I have no clue how to fix it. Been trying for hours now. I don't get what most of the validators message implies, some say open elements or errors - but I can't find them.
This all stems from your unclosed <class="contact"> "element" which should be an attribute of another element, not its own element. Most likely what you want is:
<div class="contact">Prime Properties</div>
In the future please post your code as text, not as an image.
The error messages are self explanatory. #Doelleri already spotted the <class="contact"> wierd tag...
In addition, your tag is missing a .
Ex:email
I have an control, to which I want to add a custom html attribute called, previousValue.
The Salesforce Developer's Guide assures me that I can do this by prefixing the attribute name with html-.
So I have an element that appears thus:. I also have the docType="html-5.0" attribute in my page control.
However, in Eclipse I get an 'unsupported attribute' error. I have upgraded to the latest force.com IDE; can any one tell me why this isn't working? What else do I need to do?
Thanks.
After much experimentation, the answer to this seems to be that the salesforce developer's guide is inaccurate and the 'hmtl-' prefix is not supported by the <apex:inputField> component. I can add it without a problem to an <apex:outputPanel> component. Don't understand why this should be so and the whole point to using these attributes is to locate data in a relevant place and avoid complex jquery selects to find the data relative to the location at which it is required.
I'm using mobile template HTML files on a PHPBB forum.
I tested the html for errors at http://validator.w3.org/
The test results showed the following error
Line 24, Column 66: {navlinks.FORUM_NAME}
Bad value up for attribute rel on element a: The string up is not a registered keyword or absolute URL.
Not having heard back from the author and not finding much on Google search, I'm trying to understrand what rel="up" does, if anything constructive.
Can't find any mention as an official HTML attribute
http://www.w3schools.com/tags/att_link_rel.asp
wondering if it's probably safe to just remove the phrase rel="up"
The Internet Assigned Numbers Authority (IANA) keeps a list of link relationships The latest version is from March 21 2013.
up: Refers to a parent document in a hierarchy of documents.
Unfortunately, despite the fact that this registry was long established, it was decided that HTML5 would not use this registry and would use a Wiki page to list the conforming link types instead.
Up, is listed in a rather insane section marked "dropped without prejudice", which nobody seems to know what to do with, or how to get those link types out of.
It's safe to drop it, but some browsers and browser plugins make use of it. For example, I use a Firefox plugin called "Link Widgets" like this to make use of the link type.
From: http://www.w3.org/MarkUp/html3/dochead.html
REL=Up
When the document forms part of a hierarchy, this link references the immediate parent of the current document.
If this is causing any specific problems or unexpected results, please post your code. Thanks.
Morning!
I added the following line of code to disable the skype feature on phone numbers.
<meta name="SKYPE_TOOLBAR" content="SKYPE_TOOLBAR_PARSER_COMPATIBLE" />
The problem is that it is causing the following error.
Line 6, Column 71: Bad value SKYPE_TOOLBAR for attribute name on element meta: Keyword skype_toolbar is not registered.
Syntax of metadata name:
A metadata name listed in the HTML specification or listed in the WHATWG wiki. You can register metadata names on the WHATWG wiki yourself.
Is there a work around for this? I need to ensure that the skype numbering doesn't take over the phone numbers but also validate at the same time.
Thanks for reading.
You can submit a metadata registration to the WHATWG wiki as instructed, or you can ignore the error message. Neither of these has any effect on whether your page works as intended.
Use HTML 4.01 (which lacks the HTML 5 draft's bizarre limits on what constitutes valid meta data).
I am trying to validate a page in which I have implemented Lightbox and W3C thinks rel="lightbox['gallery']" is invalid code. Code is :
<a rel="lightbox[gallery]" href="link-to-image">
...image...
</a>
Error:
Bad value lightbox[gallery] for attribute rel on element a: Keyword lightbox[gallery] is not registered.
Any insight into this is welcomed.
At least for me it's more comfortable to use "target" instead of "rel" or "data-rel" (which is not a standard link attribute anyway), thus still pass w3 HTML5 validation and do not mess with page's CSS setup ("class" is commonly used for layout and such). Of course all "*.getAttribute('rel')" in javascript source has to be updated accordingly.
You're trying to validate HTML5, right?
It's simple enough I'm afraid; whereas HTML4 allows pretty much any content in rel, HTML5 is much stricter and "lightbox[gallery]" isn't a registered rel type.
I've seen a fix which should work: get Lightbox to look for class="lightbox[gallery]" instead of rel="lightbox[gallery]", but so far my inept tweaks haven't worked. I'm trying to contact the Lightbox dev to ask him about this, but his forum is giving 500 errors. Not a good sign. :(
Or a better idea - in my opinion ofc - instead of rel use data-rel. But also you have to modify lightbox a little bit ;-)
With Lightbox2, you should use
<strong><a data-lightbox="lightbox[gallery]" href="link-to-image"></strong>
instead of
<strong><a rel="lightbox[gallery]" href="link-to-image"></strong>
This will validate as HTML5.