ustomization
and outside the scope of pagination. As such, it may be better for the HTML
to markup the structure of the content with sorting and collation but for
this to be configurable through CSS without the structural DOM changes.
This could also apply to HTML lists: , .
Thanks,
Cameron Jones
On Fri, Feb 22, 2013 at 10:05 AM, Anne van Kesteren wrote:
> On Thu, Feb 21, 2013 at 7:42 PM, Cameron Jones wrote:
> > I've just committed an initial draft of HTTP extensions for Forms:
> >
> > http://cameronjones.github.com/form-http-extensions/index.html
> >
&g
On Fri, Feb 22, 2013 at 4:37 PM, Anne van Kesteren wrote:
> On Fri, Feb 22, 2013 at 2:29 PM, Cameron Jones wrote:
> > The HTTP headers are restricted using a copy-paste of those in XHR which
> is
> > included in the form submission process. Happy to hear any suggestions
On Mon, Oct 14, 2013 at 9:04 PM, Ian Hickson wrote:
> On Thu, 21 Feb 2013, Cameron Jones wrote:
> >
> > http://cameronjones.github.com/form-http-extensions/index.html
>
> On Fri, 22 Feb 2013, Cameron Jones wrote:
> >
> > The motivations are the same which su
t; >>
> >> [ 210 000 ] [+|-]
> >> [ 19 250 ] [+|-]
> >> [ 1 500 ] [+|-]
> >
> > To me, this suggests that grouping should eventually be a CSS
> > property. But, personally, I just don't think the problem justifies a
> > workaround
U+263A /, _.. \ _\ ;`._ ,.
> Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
The type attribute is a discriminator over an otherwise
indistinguishable text value which enables machine processing which
would otherwise not be possible or be more error prone. It has value
for , and as recommended in a
alternative-proposal to w3c issue to add element:
http://www.w3.org/html/wg/tracker/issues/184
And proposal:
http://www.w3.org/wiki/User:Cjones/ISSUE-184
Thanks,
Cameron Jones
targeting.
Proposal:
http://www.w3.org/wiki/User:Cjones/ISSUE-195
Issue 195:
http://www.w3.org/html/wg/tracker/issues/195
Thanks,
Cameron Jones
On Wed, Feb 22, 2012 at 5:38 PM, Adam Barth wrote:
> Last time I asked around, there didn't seem to be much demand for
> these features so I didn't implement the previous version that was in
> the HTML spec.
>
> Adam
>
>
I've responded to repeated requests on public-html and
public-html-comments
On Wed, Feb 22, 2012 at 6:01 PM, Jukka K. Korpela wrote:
> 2012-02-22 19:30, Cameron Jones wrote:
>
>> Updating as form submittable element is included in a
>> proposal to enhance http request processing under a w3c issue
>
>
> This sounds like a pointless attem
On Wed, Feb 22, 2012 at 6:26 PM, Jukka K. Korpela wrote:
> 2012-02-22 20:13, Cameron Jones wrote:
>
>> It [the element]
>
>> does provide a greater degree of integration with the browser though.
>
> Is this a requirement, or just assumed features of implementat
If the content is a special section within the document you should use
the element which has semantic meaning over .
Alternatively you could use if it's distinct and
self-contained. These two elements serve to disambiguate the abstract
idea of content into something with semantic meaning which ca
d ,
>> is used to form an independent content like blog entry, comment, or
>> application.
>>
>> Both section and article elements are not the candidate for containing a
>> website or a blog entry's main content. That obviously is the reason that
>> the ex
; Both section and article elements are not the candidate for containing a
>>> website or a blog entry's main content. That obviously is the reason that
>>> the example of the nav in HTML5 spec doesn't use them.
>>>
>>> Regards,
>>> Ian Yang
>
13 matches
Mail list logo
