Wilson, Kimberly | 21 Aug 19:53 2014

Content-Style-Type

I was checking an index.html document on my localhost

You said this:

Line 6, Column 63: Bad value Content-Style-Type for attribute http-equiv on element meta.
    <meta http-equiv="Content-Style-Type" content="text/css" />

When you have on your own site this:
http://www.w3.org/wiki/HTML/Elements/meta

In Example A:

<meta http-equiv="Content-Style-Type" content="text/css" />

Kim Wilson, MSCIS | Systems Analyst - Sakai & IS Academic Systems | Albany Medical Center | 518-264-1055

-----------------------------------------
CONFIDENTIALITY NOTICE: This email and any attachments may contain confidential information that is
protected by law and is for the sole use of the individuals or entities to which it is addressed. If you are
not the intended recipient, please notify the sender by replying to this email and destroying all copies
of the communication and attachments. Further use, disclosure, copying, distribution of, or reliance
upon the contents of this email and attachments is strictly prohibited. To contact Albany Medical
Center, or for a copy of our privacy practices, please visit us on the Internet at www.amc.edu.
Wilson, Kimberly | 21 Aug 18:47 2014

X-UA-Compatible

I was checking an index.html document on my localhost

At the top I have <meta http-equiv="X-UA-Compatible" content="IE=edge"/>

And you're indicating it as invalid, when it isn't

Here's some information about it:

https://www.modern.ie/en-us/performance/how-to-use-x-ua-compatible

Kim Wilson, MSCIS | Systems Analyst - Sakai & IS Academic Systems | Albany Medical Center | 518-264-1055

-----------------------------------------
CONFIDENTIALITY NOTICE: This email and any attachments may contain confidential information that is
protected by law and is for the sole use of the individuals or entities to which it is addressed. If you are
not the intended recipient, please notify the sender by replying to this email and destroying all copies
of the communication and attachments. Further use, disclosure, copying, distribution of, or reliance
upon the contents of this email and attachments is strictly prohibited. To contact Albany Medical
Center, or for a copy of our privacy practices, please visit us on the Internet at www.amc.edu.
Eric Richards | 19 Aug 20:47 2014
Picon

Search engines need new <meta> keywords

I hope this the correct group to make this proposal. My apologies if
there is a error, but I hope it will be noticed and others will see
the merit and so improvements can be made with this suggestion so we
can have a better system.

I am sure you have noticed sometimes it is hard to search for
something on internet.

The suggestion is so webmasters can divide there web pages into groups
that could be used as “keywords” in the <meta> section of the web page

Such keywords might be “sales-goods”, “sales-services”, “forum”,
“tutorial”. “news”,   “organisations”,    “information”
Maybe you can think of more.

So when you go to a web search engine you tick the appropriate button
or use the keywords in the entry box.

If you want to join a golf club, to improve your golf. You put in
[golf organisations] this way you know the correct results would be
more likely to come up like a local golf cub that might want new
members and not get bogged down with heaps of shops trying to sell
“golf club sets”

Eric Richards | 19 Aug 19:56 2014
Picon

The following need to be included into the Validator.

There a error with the W3C Validator

It seems to be it does not like any of the following

Some or none of the frac options e.g.
&frac18; &frac15; &frac13; &frac38; &frac25; &frac35; &frac58;
&frac23; &frac45; &frac78;

not to mention
&incare;
&numero;

The intended web page had to be changed &#NNNN; (where NNNN is a four
digit number)  as suggested by this group to make the web page pass
the Validator, but the point is why have something like &frac18; if
one con not use it to validate a page.

ramanjeet.taneja | 18 Aug 12:46 2014

Meta Names added to the Wiki List

Hello administrator

 

I have added the following meta names to the Wiki Meta Extensions list.

 

FSDateCreation - The date when this web page was created

FSDatePublish - The date when this web page was created

FSFLContent - Informs the Publisher tool whether this page contains any content or not. Valid values yes or no

FSLanguage - Language of the content in the page. Example: US English or UK English, etc

FSOnSitemap - Whether the page is accessible via the Sitemap link in the firmsite

FSPageDescription - Description of the content of page

FSSearchable - This tag mentions whether a certain page can be searched or not

FSWritertoolPageType - Page Type of a page in the firmsite. Page Type values help the Publisher toold in page creation

FSSection - Depicts whether a page is a Section Page or simple page. Section pages can have links to other pages

FSPageName - Name of the page within a Findlaw firmsite

FLBlogAuthor - Depicts whether author of the blog is lawfirm or FL author

 

I have updated the link which is accessible for general viewership and does not require any authentication

 

Rgds

Ramanjeet

veron.nv | 17 Aug 08:28 2014
Picon

Add table keyword w3 validator

Hello!
The request to add new values which are used by CMS Xenforo to support of the table of the validator. It
"rel=up" and "rel=menu"

Example code from CMS:
<a href="{$homeLink}" class="crumb"{xen:if $microdata, ' rel="up" itemprop="url"'}><span{xen:if
$microdata, ' itemprop="title"'}>{xen:phrase home}</span></a>
<a href="{$extraTab.href}" class="SplitCtrl" rel="Menu"></a>

These values are used in several CMS templates.

Very much I ask to add in support of value and to get rid of a constant mistake in the site analysis the w3c validator.
Thanks. 

Regards.

jkorpela@cs.tut.fi | 17 Aug 19:15 2014
Picon
Picon

VS: errors

These entity references are not defined in HTML except for HTML5. If you use them you need to declare "<!doctype html>.

 

In practice, due to limited browser support, it is better to enter the characters as such, in utf-8 encoding, or use numeric character references.

 

Yucca

 

 

------ Alkuperäinen viesti------

Lähettäjä: Eric Richards<2eric.richards <at> gmail.com>

Paivays: su, 17.8.2014 1.14

Vastaanottaja: www-validator <at> w3.org;

Aihe:errors

 

Are there a errors with the W3C Validator It seems to be it does not like any of the following Some or none of the frac options e.g. &frac18; &frac15; &frac13; &frac38; &frac25; &frac35; &frac58; &frac23; &frac45;&frac&8; not to mention &incare ; &numero;
Eric Richards | 16 Aug 23:27 2014
Picon

errors

Are there a errors with the W3C Validator

It seems to be it does not like any of the following

Some or none of the frac options e.g.
&frac18; &frac15; &frac13; &frac38; &frac25; &frac35; &frac58;
&frac23; &frac45;&frac&8;

not to mention
&incare ;
&numero;

Pluto is a Planet | 16 Aug 01:57 2014
Picon

[VE][79] Horizontal Rule <hr> Tags Break Paragraphs

Error [79]: "end tag for element X which is not open"

Here’s an example, which validates the same way in Firefox, the W3C Validator (in 4.0.1 and 5), and in jsfiddle: http://jsfiddle.net/Lraps5oy/

While the reference states that any flow elements are permitted as parents (including the <p> tag), the <hr> tag breaks a paragraph it’s contained in so that it’s considered the end tag of a <p> tag. If you do have a closing </p> tag or text content after an <hr> tag, it’ll be considered an error.

One of the details mentioned with this error is that it can be caused “by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case),” which seems to make sense, except there is no error in validating the <hr> tag (nor should there be based on the specification).

Pluto
ramanjeet.taneja | 8 Aug 10:05 2014

HAve added new meta names to the Wiki-MetaExtentions

Hello I have added the following meta names to the Wiki-MetaExtentions. Request you to please update the validators with these new terms.

 

Keyword

Brief Description

FSDateCreation

The date when this web page was created

FSDatePublish

The date when this web page was last published. Published implies, the modified page is accessible through Internet

FSFLContent

Informs the Publisher tool whether this page contains any content or not. Valid values yes or no

FSLanguage

Language of the content in the page. Example: US English or UK English, etc

FSOnSitemap

Whether the page is accessible via the Sitemap link in the firmsite

FSPageDescription

Description of the content of page

FSSearchable

This tag mentions whether a certain page can be searched or not

FSWritertoolPageType

Page Type of a page in the firmsite. Page Type values help the Publisher toold in page creation

FSSection

Depicts whether a page is a Section Page or simple page. Section pages can have links to other pages

FSPageName

Name of the page within a Findlaw firmsite

 

Regards

Ramanjeet

ARPITA BAHUGUNA | 8 Aug 10:06 2014

New 'contact' meta extension added to the whatwg meta extensions wiki

Hi,

 

This is to inform you that we have added a new 'contact' meta extension to http://wiki.whatwg.org/wiki/MetaExtensions.

 

Brief description:

Defines the vendor's contact information by way of a phone-number (such as the customer support number), an e-mail ID (such as the customer support mail ID) or a physical address (such as the office address or billing address).
Usage: <meta name="contact" content="+1-555-555-5555 abc <at> xyz.com '5844 South Oak Street, Chicago, Illinois'">
or in case of multiple entries:
<meta name="contact" content="Chicago: +1-555-555-5555 abc <at> xyz.com '5844 South Oak Street, Chicago, Illinois'; Brookfield: +1-444-444-4444 def <at> xyz.com '2341 Cherry Lane, Brookfield, Illinois'">
The content attribute is a space separated string containing the phone-number followed by the e-mail ID and then the address (specified within quotes).
For specifying multiple entries a semi-colon separated list of name: value pairs can be defined. The name can be any descriptive tag identifying the given location.
Valid phone numbers and mail IDs should be provided by the vendor. The address can either be a string specified within quotes or the latitude and longtitude coordinates.

 

Documentation:

http://arpita.github.io/ContactMetaExtensions/

 

Request you to kindly verify the same and pull in the change.

 

Regards,

Arpita Bahuguna


Gmane