w3c

W3C validator says 'feed does not validate' 'url must be a full URL'… whats wrong with it?

给你一囗甜甜゛ 提交于 2019-12-03 16:54:09
问题 Validating my feed, it has an enclosure with a URL of https://archive.org/download/NigelFarageAPersonalMessageToNorthernIrelandVoters./Nigel%20Farage,%20a%20personal%20message%20to%20Northern%20Ireland%20voters..mp3 I know it is a bit convoluted... but what is wrong with it? The stop in the directory name? the double dot in the file name? the comma? all of em? I have looked at the RFC on URL's but cant make it out(!). This feed does not validate. line 441, column 2: url must be a full URL:

Rails - Parameter with multiple values in the URL when consuming an API via Active Resource

让人想犯罪 __ 提交于 2019-12-03 15:44:45
问题 I am consuming an API that expects me to do requests in the following format: ?filter=value1&filter=value2 However, I am using Active Resource and when I specify the :params hash, I can't make the same parameter to appear twice in the URL, which I believe is correct. So I can't do this: :params => {:consumer_id => self.id, :filter => "value1", :filter => "value2" } , because the second filter index of the hash will be ignored. I know I can pass an array (which I believe is the correct way of

Selenium JSON Wire Protocol vs Webdriver Wire Protocol

亡梦爱人 提交于 2019-12-03 13:17:02
I have seen that the JSON Wire Protocol is obsolete and the Webdriver Wire Protocol is the new implementation. I want to understand what changes to implement in the Webdriver Wire Protocol and how it is different from the JSON Wire Protocol ? Here are the naming conventions that have changed: JSON Wire Protocol WebDriver Wire Protocol version browserVersion platform platformName noProxy noproxy UnknownCommand unknown command NoSuchFrame no such frame NoSuchElement no such element StaleElementReference stale element reference ElementIsNotSelectable element not selectable JavaScriptError

Opengraph W3C valid?

早过忘川 提交于 2019-12-03 13:11:14
I would like to know if the opengraph markup is W3C valid, I'm getting the following error when I try to validate it: Line 14, Column 17: there is no attribute "PROPERTY" <meta property="og:site_name" content="sitename"> In case it's not valid, will it impact my pagerank and other search engines algo? Is it possible to cloak those properties? bobince It's not valid in the normal HTML doctypes, but there is a doctype you can use to validate XHTML documents including Open Graph: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd"> See this

HGROUP element removed from the HTML5 Specification. What alternative technique can be used instead?

倖福魔咒の 提交于 2019-12-03 12:29:47
As some of you would of heard the hgroup element is being removed from the HTML5 Specification . (For more info, see the W3C HTML Working Group's decision on request to drop hgroup from HTML5 on the W3C's Public Mailing List archives.) Now I'm currently working on the redesign of a site using this tag that creates a way of adding a sub heading. My current thoughts are to just add another hX tag under the main header, but I'm not sure if this would be semantic enough to do so. <h1>Darren Reay</h1> <h2>A developing web developer</h2> <p>Hello World</p> Could anyone either come up with a

W3C HTML validation for React JSX files

◇◆丶佛笑我妖孽 提交于 2019-12-03 12:12:59
When working on front-end projects I always like to work with linting tools. They prevent from dumb mistakes to serious smelly code pieces. Linting tools also suggest improvements and optimisations. Validating and linting HTML means using the W3C Validator. When working with vanilla JavaScript projects I use the grunt-html Grunt NPM module. And when working with Angular 1.x I use the grunt-html-angular-validate module, which is the same validator but adapted to Angular requirements (non standard attributes or incomplete HTML documents will not fire errors or warnings). However I have tried to

Can a label only refer to input elements?

非 Y 不嫁゛ 提交于 2019-12-03 10:54:06
W3Schools have this to say about labels : The <label> tag defines a label for an input element. [Emphasis mine] Does this mean that the following HTML isn't valid? <!doctype html> <html> <head> <title>Example document</title> </head> <body> <label for="x">Label</label> <hr> <div id="q" contentEditable="true">Hello</div> <hr> <div id="x" contentEditable="true">World</div> </body> </html> Both Chrome and IE8 give focus to World when Label is clicked, Firefox does not. Which is correct? According to the W3C it applies to Form Controls, and Form Controls are defined as : Buttons Checkboxes Radio

Why was ::selection removed from the CSS Selectors spec, and how does its specificity work against type selectors?

假装没事ソ 提交于 2019-12-03 05:56:59
Some questions about using CSS to specify the color of selected text: https://developer.mozilla.org/En/CSS/::selection says that, ::selection was drafted for CSS3 Selectors but removed from the current CSS3 draft. Anyhow, it's implemented in browsers and support will continue. Why was it removed? Imagine that a rule like the following exists in the default CSS that's implemented by the browser: ::selection { background-color: Highlight; color: HighlightText; } Further imagine that a rule like the following is defined in any site-specific authored stylesheet: body { background-color: white }

Is Scala/Java not respecting w3 “excess dtd traffic” specs?

僤鯓⒐⒋嵵緔 提交于 2019-12-03 05:07:02
问题 I'm new to Scala, so I may be off base on this, I want to know if the problem is my code. Given the Scala file httpparse, simplified to: object Http { import java.io.InputStream; import java.net.URL; def request(urlString:String): (Boolean, InputStream) = try { val url = new URL(urlString) val body = url.openStream (true, body) } catch { case ex:Exception => (false, null) } } object HTTPParse extends Application { import scala.xml._; import java.net._; def fetchAndParseURL(URL:String) = { val

Correct way to include CSS after <head>

荒凉一梦 提交于 2019-12-03 01:49:55
Apparently adding <link rel="stylesheet" ... in the document body is considered a bad practice by W3C standards. The same for adding <style> blocks in the body... So are there any standard-compliant solutions to add CSS outside of the <head> tag? Like at the end of the document. If you only want to include your CSS styles on a specific events, there's nothing stopping you from doing so at the head: var linkElement = document.createElement("link"); linkElement.rel = "stylesheet"; linkElement.href = "path/to/file.css"; //Replace here document.head.appendChild(linkElement); This has the added