On Wed, Jun 24, 2015 at 3:46 AM, timeless timel...@gmail.com wrote:
The trailing dot actually had meaning, but in my periodic testing most
commerce websites didn't handle it well. It didn't help that browsers never
favored adding it.
On a somewhat (user) hostile network, http://discover.com/
The trailing dot actually had meaning, but in my periodic testing most
commerce websites didn't handle it well. It didn't help that browsers never
favored adding it.
On a somewhat (user) hostile network, http://discover.com/ might go to
http://discover.com.example.com/ this probably isn't what
Florian Rivoal wrote:
If a text input field has lang=foo, and your system has a (virtual)
keyboard for language foo, I would expect that keyboard to be the one
presented to you.
The principle of least surprise argues against this.
Most mobile phones support many more languages and keyboard
On Jun 23, 2015, at 22:57, Mark Simon m...@manngo.net wrote:
(This is my first post here, so I’m not sure about appropriate protocols).
HTML5 adds more power to the heading elements, which is a good thing.
However, there appears to be no recommended element for marking up a
site-wide
http://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?url=https://raw.githubusercontent.com/masinter/multipart-form-data/master/multipart-form-data.xmlmodeAsFormat=html/asciitype=ascii
Encoding considerations:Common use is BINARY.
In limited use (or transports that restrict the encoding to 7BIT or
On 24 Jun 2015, at 13:07, timeless timel...@gmail.com wrote:
Florian Rivoal wrote:
If a text input field has lang=foo, and your system has a (virtual)
keyboard for language foo, I would expect that keyboard to be the one
presented to you.
The principle of least surprise argues against
On Wed, Jun 24, 2015 at 1:50 PM, Tim Streater t...@clothears.org.uk wrote:
On 24 Jun 2015 at 20:15, Peter Kasting pkast...@google.com wrote:
1.66 = 1.0.0.66
1.256 = 1.0.1.0
1.2.66 = 1.2.0.66
1.256.66 = invalid
This makes no sense at all.
On Wed, Jun 24, 2015 at 2:36 PM, Maciej Stachowiak m...@apple.com wrote:
To close the loop on this, we will change to link rel=mask-icon
href=whatever.svg color=#aabbcc. We like the idea of determining the
color from the SVG, but we won't be able to implement in time for this cycle,
and
On 24/06/2015 9:08 pm, Jonathan Zuckerman wrote:
On Jun 23, 2015, at 22:57, Mark Simon m...@manngo.net wrote:
(This is my first post here, so I’m not sure about appropriate protocols).
HTML5 adds more power to the heading elements, which is a good thing. However,
there appears to be no
On Jun 23, 2015, at 22:57, Mark Simon m...@manngo.net wrote:
Presumably, the correct element is h1 for the banner heading, but this
may be at odds with the notion that h1 should describe the specific
page.
The banner title would be expected to be the same for most, if not all,
pages, while the
On 24 Jun 2015 at 20:15, Peter Kasting pkast...@google.com wrote:
How Chrome's omnibox handles this (which I think is compliant with most
other places):
If there are no dots in the middle of the expression, the number is
converted to powers-of-256 format and leading 0s are prepended to
To close the loop on this, we will change to link rel=mask-icon
href=whatever.svg color=#aabbcc. We like the idea of determining the color
from the SVG, but we won't be able to implement in time for this cycle, and
having an explicit color override seems useful. So for now we'll implement
On Wed, Jun 24, 2015 at 3:46 AM, timeless timel...@gmail.com wrote:
Also fun and probably worth documenting is how http://127.1/ and
http://127.2.1/ are parsed. I doubt the average developer knows (unless they
specifically deal with low level networking).
The question is whether the parsing
On 6/24/15, Barry Smith bearzt...@live.com wrote:
On Jun 23, 2015, at 22:57, Mark Simon m...@manngo.net wrote:
Hi Barry —
When I build a website that is to have more than one page, and I want the
banner to be the same across all pages, I use the header element with
a
javascript file
On 06/24/2015 08:33 PM, Kevin Marks wrote:
Does this mean we can now have rel=icon with SVG instead of providing a
bitmap for every iOS device specifically (when we add to homepage)? Do
chrome and Firefox support SVG icon images?
Here's a simple testcase:
Does this mean we can now have rel=icon with SVG instead of providing a
bitmap for every iOS device specifically (when we add to homepage)? Do
chrome and Firefox support SVG icon images?
On 24 Jun 2015 2:40 pm, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Wed, Jun 24, 2015 at 2:36 PM, Maciej
On Wed, Jun 24, 2015 at 7:21 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Wed, Jun 24, 2015 at 3:46 AM, timeless timel...@gmail.com wrote:
You have http://0.0.0.66/ that's not a match for your example...
I'm not sure what you mean here.
You swap between 0.0.0.66 and 66.0.0.0 in your OP.
On Wed, Jun 24, 2015 at 9:23 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Wed, Jun 24, 2015 at 9:06 AM, Tab Atkins Jr. jackalm...@gmail.com wrote:
You swap between 0.0.0.66 and 66.0.0.0 in your OP.
Actually, the input URL in that case is different. 0x42.0. != 0x42.
Well *that's*
On Wed, Jun 24, 2015 at 9:06 AM, Tab Atkins Jr. jackalm...@gmail.com wrote:
You swap between 0.0.0.66 and 66.0.0.0 in your OP.
Actually, the input URL in that case is different. 0x42.0. != 0x42.
--
https://annevankesteren.nl/
On Wed, Jun 24, 2015 at 9:37 AM, Tab Atkins Jr. jackalm...@gmail.com
wrote:
On Wed, Jun 24, 2015 at 9:23 AM, Anne van Kesteren ann...@annevk.nl
wrote:
On Wed, Jun 24, 2015 at 9:06 AM, Tab Atkins Jr. jackalm...@gmail.com
wrote:
You swap between 0.0.0.66 and 66.0.0.0 in your OP.
20 matches
Mail list logo
