404
results for "microformats hard"
-
We can have PHP unit skip the test when not on the optional parser. That's not too hard. But can it run the tests twice?
Zegnat
at
2018-03-27 18:40
-
it is not hard to implement, just that we would be iterating over the DOM tree so many times
KartikPrabhu
at
2018-03-26 21:51
-
That backcompat stuff is hard, which is why I like focussing on some new stuff. Like white spacing ;)
Zegnat
at
2018-03-25 20:46
-
Could be. It is just very hard to manually check what the right result should be for something like https://github.com/Zegnat/microformats-tests/blob/zegnat-master/tests/microformats-v2/h-entry/urlincontent.html
Zegnat
at
2018-03-24 18:16
-
Because e-* parsing is incredibly hard to do by hand
Zegnat
at
2018-03-24 17:50
-
Should the expected output here be updated? Sorry, I'm still having a hard time wrapping my mind around expected output for 'rels': http://microformats.org/wiki/microformats2-parsing#rel_parse_examples
gRegorLove
at
2018-03-21 19:26
-
As soon as my morning tea is at my side. Having a hard time getting started today
Zegnat
at
2018-03-21 08:00
-
I'm just having a hard time following the whole discussion, what should/shouldn't be ordered. Could just be tiredness on my end. I'm not 100% today.
gRegorLove
at
2018-03-19 22:44
-
so before you work too hard on backcompat for that, might try going through /hreview-examples-in-wild
tantek
at
2018-03-18 01:50
-
Hard to say without looking at old usage, KartikPrabhu. If there is presedence for multiple fn’s meaning multiple items, then no. But I would think multiple items just hard require the `item` class to have been used in the mf1.
Zegnat
at
2018-03-18 01:49