338 results for "microformats hard"

  • Are microformats supposed to work if they are client-side generated / added to the DOM by JavaScript? That sounds kind of hard to consume without actual browser.
    ccx at 2022-02-22 01:04
  • Err, I've meant it's hard to tell one should parse the site for microformats. But the same difficulty applies to regular feeds.
    ccx at 2022-02-22 00:18
  • It wouldn't be too hard to add h-dir, h-file, p-mod-time, p-size, etc to that listing and make it machine readable
    Anders at 2022-02-19 00:40
  • Good to know! I don’t know how hard this will be to tackle but I’ll take a look.
    capjamesg[d] at 2022-02-18 23:57
  • The usecase that is still hard to mark up is the calendar grid for events where you have time down and different tracks across.
    [KevinMarks] at 2022-02-08 00:45
  • duration isn't too hard (thanks regex)
    jacky at 2022-02-07 23:34
  • jacky: sknebel left you a message 8 hours, 15 minutes ago: "so a test failed b/c it's mentioned h-org as a type (the parser does hard failures on unrecognized types)" <- there is no concept of "recognized" types in mf2 parsing! don't do that please
    Loqi at 2022-02-06 19:48
  • !tell jacky "so a test failed b/c it's mentioned h-org as a type (the parser does hard failures on unrecognized types)" <- there is no concept of "recognized" types in mf2 parsing! don't do that please
    sknebel at 2022-02-06 11:32
  • I don't think it's expected to have actually hard failures
    jacky at 2022-02-06 09:26
  • so a test failed b/c it's mentioned h-org as a type (the parser does hard failures on unrecognized types)
    jacky at 2022-02-06 09:24
Sort by:

Filter results by:

Tag

Query took 0.01s.


Search tips

Exclusion
+foo -bar
Logical OR
foo OR bar
Exact phrase
"foo bar"
Partial words
foo*
Particular fields only
title:foo
domain:example.org
nick:somebody
after:2016-11-23
before:2016-11-23
date:2016-11-23