00:06
<brandon>
I am guessing this is several days late, but I ran into a limitation I wasn't expecting (assumed it was in the spec). The problem I am having is placing a background of rgba(0,0,0,.2) OVER a background image... but background colors are only allowed to be declared last (after all other images)... The only other solution (without adding more markup or changing the image itself) is to set a...
00:06
<brandon>
...transparency to the background (with a background color of black)... Is there any way of getting something similar into the spec? Or is there something I'm missing?
00:50
<bfrohs>
Anyone?
00:53
<Lachy>
bfrohs, yeah, be with you in a minute...
00:53
<bfrohs>
Thanks.
00:57
<Lachy>
bfrohs, try using the ::before pseudo-element, which you can style and position on top of the element with the background image.
00:57
<bfrohs>
Very good idea, thanks. I'll let you know how it works out.
00:58
<Lachy>
here's a quick demo http://software.hixie.ch/utilities/js/live-dom-viewer/saved/338
01:01
<bfrohs>
Doesn't work with content inside the tag
01:01
<bfrohs>
Pushes it down - also doesn't work with liquid element
01:02
<bfrohs>
http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cstyle%3E%0Adiv%20{%20height%3A%2099px%3B%20width%3A%20200px%3B%20background%3A%20url%28image%29%20}%0Adiv%3A%3Abefore%20{%20display%3A%20block%3B%20height%3A%2099px%3B%20width%3A%20200px%3B%20background%3A%20rgba%280%2C0%2C255%2C.5%29%3B%20content%3A%20%22%22%20}%0A%3C%2Fstyle%3E%0A%3Cdiv%3Ehai%3C%2Fdiv%3E
01:08
<Lachy>
bfrohs, set position: absolute; on the ::before
01:09
<bfrohs>
I already did that, but it doesn't account for the fact that it doesn't work with liquid content
01:09
<bfrohs>
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/339
01:10
<bfrohs>
Well, hold on.
01:10
<bfrohs>
Yeah, even with Overflow:hidden, it doesn't work
01:14
<Lachy>
bfrohs, set position: relative; on the div, so that the absolute positioning on the ::before is contained within it
01:16
<bfrohs>
Setting position to relative hides the :before completely (with 100% width and height to account for fluid elements)
01:17
<bfrohs>
And it also pushes the content down when any other height is set (5em for example)
01:18
<Lachy>
huh?
01:18
<Lachy>
seems to work for me. But I'm not sure what exactly you're doing
01:23
<bfrohs>
Could you send me your file?
01:24
<bfrohs>
I may have just mistyped something.
01:24
<Lachy>
http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0D%0A%3Cstyle%3E%0D%0Asection%20%7Bdisplay%3Ablock%3B%20background%3A%23f00%3B%7D%0D%0Adiv%20%7B%20background%3A%20url(image)%3B%20position%3A%20relative%3B%20%7D%0D%0Adiv%3A%3Abefore%20%7Bposition%3Aabsolute%3Bdisplay%3A%20block%3Bheight%3A100%25%3Bwidth%3A%20100%25%3B%20background%3A%20rgba(0%2C0%2C255%2C.5)%3B%20content%3A%20%22%22%20%7D%0D%0A%3C%2Fstyle%3E%0D%0A%3Csection%3E%
01:24
<Lachy>
0D%0A%3Cdiv%3Exxx%0D%0A%3Cp%3Ehai%3Cp%3Ehai%3Cp%3Ehaifdsli%20fdsajfdkls%20ajflkdsj%20afldsja%20fldsjaflkds%20jflsdj%20afdsjlfdjsl%3Bfdjslfds%3C%2Fdiv%3E%3C%2Fsection%3E
01:27
<bfrohs>
You're a life saver! Thanks!
01:27
<Dashiva>
"A PublicIdentifier SHOULD NOT be used unless the content is being managed in a controlled environment where the intended version is known"
01:28
<Dashiva>
Isn't it sort of redundant to specify the version in the doctype if one of the premises is that the version is already known?
01:30
<Lachy>
bfrohs, be sure to use :before with one colon instead of two, if you want it to work in IE. Though, I'm not sure what other issues might crop up with it since I haven't tested it at all with what I did
01:31
<bfrohs>
Yeah, always do. And I'll be sure to test it, thanks Lachy.
01:36
<bfrohs>
Lachy, I've run into a problem with it. It applies the background (of the :before) on top of the text as well (hence why I'm using rgba vs opacity)
01:43
<Lachy>
oh, then I think the only solution would be to use 2 elements. One with the background image and the other on top with the background colour and text
01:45
<Lachy>
or, maybe not. one sec...
01:46
<Lachy>
bfrohs, set z-index: -1; and specify the background image on on ::before, and then specify the colour on the element. That will give you the correct layering of text, bg colour, bg image
01:55
<bfrohs>
Doesn't work either. Only works if there isn't a parent with a declared background
01:56
<bfrohs>
Thanks though Lachy! I'll get ahold of the CSS wg
02:20
<TabAtkins>
bfrohs: It should still work, you'll just need to be more careful and explicit about z-ordering.
02:20
<TabAtkins>
Your problem is that the parent with the declared background is layering on top of the ::before
02:27
<bfrohs>
Yes, I know, but it's not just a signle element (nor a fixed size). It's built into a web application (programmed myself) that would have several elements (all at different depths in the DOM) with this class.
02:51
<TabAtkins>
bfrohs: Ah, then you're in trouble. Obvious (though annoying) hack around this: a 1px partially-transparent image.
06:09
<MikeSmith>
Hixie: the ABNF for the text content of the style element doesn't seem to allow <style><!--></style>
06:09
<MikeSmith>
but back in the "escaping text span" days, that was conformant
06:09
<MikeSmith>
is it intentional that it should be non-conformant now?
06:10
<Hixie>
it's non-conforming according to CSS anyway
06:10
<MikeSmith>
OK
06:10
<Hixie>
but off-hand i don't know if zcorpan (or hsivonen? i forget who came up with what the rules should be) wanted that to conform or not
06:10
<Hixie>
i don't see a use case for having it conforming though, so...
06:11
<MikeSmith>
OK, I'll ask them later if they have any cases
06:11
<MikeSmith>
was asking because I'm attempting right now to write a mechanism for validator.nu to check style contents, based on that ABNF
06:12
<MikeSmith>
if that were to be conforming, it'd mean adding an additional state
06:13
<MikeSmith>
Hixie: btw, why "c-start" and "c-end" ?
06:13
<MikeSmith>
what's the "c" for?
06:13
Hixie
looks at what c-start is
06:14
<Hixie>
comment-start
06:14
<MikeSmith>
ah
06:14
<MikeSmith>
well, it's not a comment...
06:14
<MikeSmith>
it's more of an escape
06:15
<Hixie>
it's just an opaque string really
06:15
<Hixie>
the only thing in that ABNF that matters is "style"
06:15
<Hixie>
everything else is a spec implementation detail
06:15
<Hixie>
could be "a", "b", "c", etc
06:17
<MikeSmith>
yeah, I know.. was asking because I wanted to have state names that are less opaque
06:17
<MikeSmith>
so I'm using ESCAPE
07:18
<Hixie>
mjs: "We follow a similar process for Safari, except that we don't usually test if a site works in Chrome first, since that rarely comes up"
07:18
<Hixie>
ooh, burn :-)
07:30
<MikeSmith>
Hixie: is "<style><!-- </style --></style>" meant to be conformant?
07:31
<Hixie>
yes
07:31
<Hixie>
the only requirement is that each <!-- be followed by a --> before the end and before another <!--
07:31
<MikeSmith>
OK
07:31
<Hixie>
no even that's wrong
07:32
<Hixie>
the only requirement is that each <!-- be followed by a --> before the end
07:32
<MikeSmith>
OK
07:32
<Hixie>
(ignoring <!--s between a <!-- and a -->)
07:32
<Hixie>
it's hard to say in english
07:32
<Hixie>
hence the ABNF :-)
07:32
<MikeSmith>
yeah
07:32
<Hixie>
<style> is the one with the wacky rules
07:32
<Hixie>
er
07:32
<Hixie>
<script>
07:32
<Hixie>
i'm still on vacation. my brain will be turned on on monday. :_)
07:32
<MikeSmith>
heh
07:33
<Hixie>
good luck with implementing 4.3.1.2 and 4.3.1.3 at the same time btw
07:33
<MikeSmith>
well, I wonder if hsivonen might need to make change to his HTML parser
07:33
<Hixie>
(i.e. i hope you're doing it from code and not some schema language that only accepts one abnf per element)
07:34
<MikeSmith>
Hixie: doing it from a normal state machine
07:34
<Hixie>
well for <script> in certain cases you have to check it against two grammars
07:34
<Hixie>
and i ain't merging them
07:34
<MikeSmith>
heh, OK :)
07:34
<Hixie>
i had enough trouble writing them as it is :-P
07:35
<MikeSmith>
I will leave <script> for after <style>
07:35
<Hixie>
i think the reason i didn't call c-start "escape" is because i did the script one first and it already has an "escape", btw
07:35
<Hixie>
and a "comment"
07:36
<Hixie>
and i was trying to keep them vaguely off each other's toes
07:36
<MikeSmith>
ok, np .. I can see that for the spec it's not a problem for it to just be opaque
07:36
<MikeSmith>
had been just trying to decide on something meaningful to put in the code
07:37
<MikeSmith>
so, seems like hsivonen parser gets to "<style><!-- </style " and switches to before-attribute-name state
07:38
<MikeSmith>
or before that gets to tag-name state, I guess
07:39
<MikeSmith>
I guess I'll ask him about it when he gets back
07:40
<Hixie>
oh i didn't think of that
07:40
<Hixie>
yes, that sounds right
07:40
<Hixie>
sorry i was thinking about it from a DOM point of view
07:40
<MikeSmith>
oh
07:40
<Hixie>
and assuming that you meant a "style" element with "<!-- </style -->" as its only text node child
07:41
<Hixie>
the literal markup, even assuming it had a DOCTYPE and all, wouldn't be valid because "--" isn't a valid attribute and there's an unexpected </style>
07:41
<MikeSmith>
OK
07:42
<MikeSmith>
so the current parser behavior is right?
07:43
<Hixie>
it sounds right but what do i know
07:43
<Hixie>
i only work here
07:43
<MikeSmith>
heh
07:43
<Hixie>
ask me again in a few days if you want a more coherent answer :-)
07:43
<MikeSmith>
ok, sure
07:43
<MikeSmith>
OK, fwiw, what I have for <style> checking is live on http://qa-dev.w3.org:8888/
07:44
<Hixie>
cool
07:45
<MikeSmith>
Hixie: btw, take a look at http://qa-dev.w3.org:8888/?doc=http%3A%2F%2Fdev.w3.org%2Fhtml5%2Ftests%2Fvalidation%2Ffull%2Finvalid%2Fmissing-attributes%2Flink-missing-href.html&showsource=yes
07:45
<Hixie>
ooh, much nicer
07:45
<MikeSmith>
yeah, that one took some work
07:46
<Hixie>
i hope henri hides notes #1 and #2 from the default UI at some point
07:46
<MikeSmith>
I guess those don't bother me since I've just habituated to reading past them
07:47
<MikeSmith>
but I can see that for new users they might be not optimal
07:47
<Hixie>
well at some point i assume this will get some more serious UI review and testing... but that can wait until the backend is solid :-)
07:47
<Hixie>
i hope we get some competition for henri
07:48
<MikeSmith>
yeah, but he has set the bar pretty high
07:48
<Hixie>
this luvvy-duvvy w3c working with henri thing is ruining the plan for making validation into a tool rather than an authority
07:48
<MikeSmith>
heh
07:49
<MikeSmith>
btw, about that required-attributes reporting, whether it actually gets deployed will depend on if hsivonen thinks how I implemented it is sane
07:49
<Hixie>
heh
07:49
<Hixie>
bbiab, dinner
07:49
<jtbandes>
What language is used to implement the validator?
07:49
<MikeSmith>
ttyl
07:50
<MikeSmith>
jtbandes: a couple different things
07:50
<MikeSmith>
but basically Java
07:50
<jtbandes>
obligatory: ew java :P
07:50
<jtbandes>
Why java?
07:51
<MikeSmith>
for one thing, because the validator architecture is based on SAX, and Java has solid SAX support
07:51
<MikeSmith>
and for another thing, because of the abundance of useful libraries in Java
07:52
<MikeSmith>
but those are just my understanding
07:52
<MikeSmith>
if you want the real details, ask hsivonen
07:52
<MikeSmith>
jtbandes: or read his thesis
07:52
MikeSmith
goes to find URL for hsivonen thesis
07:52
<jtbandes>
Hm
07:53
<MikeSmith>
http://hsivonen.iki.fi/thesis/html5-conformance-checker.xhtml
07:53
<MikeSmith>
jtbandes: platform portability was another concern, I think
08:04
<MikeSmith>
Hixie: (when you get back) as far as 4.3.1.2 and 4.3.1.3, I think from the pov of the v.nu backend, those can be implemented as two different checkers (separate classes) .. so hopefully no need code-wise to merge handling of those
08:04
MikeSmith
steps out for a bit
09:10
<hsivonen>
jtbandes: see 3rd question under http://about.validator.nu/#faq
09:12
<zcorpan>
hmm, <style><!--> opens an escape in opera, so i don't mind it being invalid :)
09:22
<othermaciej>
Hixie: I imagine it's only because Chrome hasn't been around long enough yet for sites to depend on its quirks - I expect it may start happening at some point
09:23
<Hixie>
oh i wasn't disagreeing with you :-)
09:42
<zcorpan>
whatwg spec has dropped in google results for "html5"
09:43
<zcorpan>
probably due to the title change
10:31
<Hixie>
othermaciej: what's the difference between a personal opinion of a chair and an official opinion of a chair? i'm confused.
10:32
<annevk>
maybe he thought you meant the position of the chairs
10:32
<Hixie>
?
10:32
<Hixie>
as opposed to what?
10:32
<annevk>
his position
10:33
<othermaciej>
to use a particularly flame-baiting analogy, the pope does not always speak ex cathedra
10:34
<othermaciej>
in other words, I stand by my opinion, but I haven't even asked my co-chairs about it, let alone gotten their sign-off, so it's a little dicey to call it "guidance from the chairs"
10:35
<Hixie>
dude if every time i ask you a question you need to get two other people to sign off on it, our conversations aren't going to be very quick.
10:35
<othermaciej>
definitely not required every time
10:35
<othermaciej>
but I need space for posting purely personal opinions
10:36
<othermaciej>
otherwise I'll either end up posting much less, or make people mad for making improper official statements
10:37
<othermaciej>
in this case, no one asked me a question at all, I just provided my opinion unasked
10:39
<Hixie>
man i miss the days where we didn't have to worry about having personal opinions vs official opinions vs charters and so forth and we could just worry about what we thought the right thing for the web was
10:42
<othermaciej>
in this case I wouldn't have worried about the difference if you hadn't cited what I meant to be "Maciej's opinion" as "guidance from the chairs"
10:42
<othermaciej>
that being said, I realize I took on that sort of hazard when I agreed to accept a political position
10:43
<Hixie>
i hadn't realised there was a difference, i assumed when one of the chairs gave guidance, it was guidance from the chairs :-)
10:43
<othermaciej>
that's like saying every time Joe Lieberman gives a speech, that's guidance from the US Senate
10:44
<Hixie>
yes
10:44
<Hixie>
which it is
10:44
<hsivonen>
seems more correct to refer to guidance from Maciej or guidance from Joe Lieberman
10:45
<Hixie>
certainly more precise, dunno about more correct
10:45
<hsivonen>
what I say here isn't guidance from Mozilla
10:48
<Hixie>
what's the difference?
10:48
<othermaciej>
there are times when what I say is on behalf of some group or organization of which I am a member, but it certainly can't be on behalf of all of them every time
10:49
<Hixie>
i guess the difference is that i don't see input from a company or from a random person as being any different, but i see the chairs as having authority
10:50
<nessy>
so are all your opinions opinions of Google?
10:50
<Hixie>
google's employees have many opinions, all of which are often aired in public
10:50
<Hixie>
s/'s//
10:51
<othermaciej>
indeed, the chairs have authority, and many times when I speak I do not intend to wield the authority of the chairs
10:51
<Hixie>
nessy: but certainly google managers assume that everything we say reflects on google, i don't get to say "oh well i didn't mean that as a google employee"
10:51
<othermaciej>
whether it is realistic to expect that is another matter
10:54
<annevk>
I don't get Larry's real world... If it's his real world, surely he'd know the answer?
10:54
<nessy>
just being facetious - I we're all in the same position with the companies that we represent :-)
10:55
<Hixie>
nessy: yes, that's why i was surprised by maciej's e-mail
10:55
nessy
goes checking out email
10:56
<Hixie>
othermaciej: i guess i still think that there's a difference between a random person describing their opinions, and a chair describing their opinion, and i would consider the latter guidance regardless of whether it was a proclamation of chair consensus or not
10:57
<othermaciej>
Hixie: fair enough, and if you said "guidance from one of the chairs", I would not complain
10:57
<Hixie>
othermaciej: because in the absence of more data, all we have so far is a bunch of people arguing about what the group should do, and one chair saying what their opinion is
10:57
<Hixie>
othermaciej: and at the ond of that day, the chairs get to decide
10:57
<othermaciej>
(unless I tried to draw some clear distinction that I'm speaking in some other role, such as representing Apple)
10:58
<Hixie>
fair enough
10:58
<Hixie>
it's sad that we can't necessarily assume that our chairs are of one mind on matters as key as what the target audience of the main wg deliverable is, though :-)
10:59
<nessy>
maybe they are, but maciej is just careful?
11:00
<nessy>
I find that thread weird anyway … but that's just me :)
11:00
<othermaciej>
I've never actually asked them because it hasn't often been a relevant point of debate
11:00
<othermaciej>
I think Larry is trying to establish some basic points that would support his argument that HTML5 should have an optional version indicator
11:02
<othermaciej>
I doubt he'll get everyone to agree, but it beats his original approach of not stating a rationale at all
14:16
<Huvet>
hi, did someone remove the documentation? http://code.google.com/p/html5lib/wiki/UserDocumentation
14:16
<Huvet>
linked from the startpage
14:27
<Huvet>
or, I could ask what I wanted to know instead :)
14:28
<Huvet>
how do I strip all HTML from a page with html5lib?
14:28
<Huvet>
(python version)
14:38
<TabAtkins>
Different question: whitespace collapse is just a display effect, right? The original whitespace is still present in the DOM?
14:42
<hsivonen>
TabAtkins: it's in the DOM
14:42
<hsivonen>
TabAtkins: however, CRLF normalization takes place before the DOM
14:42
<TabAtkins>
hsivonen: Excellent.
14:53
<cardona507>
hey TabAtkins - how are you doing? Did you have a nice holiday? Did you ever post the CSS3 presentation from TPAC? I still haven't seen it.
14:54
<TabAtkins>
Yo, cardona507. I finished it up and sent it off to TBL. He put up an early cut without the slides, but I haven't heard anything about it since then either.
14:56
<TabAtkins>
http://www.vimeo.com/7480616
14:56
<TabAtkins>
^^^ Early one.
14:56
<mikekelly>
hi fans
14:58
<mikekelly>
been trying to figure out why there's no @rel attribute for form elements
14:59
<mikekelly>
anyone got any idea why that might be the case?
14:59
<cardona507>
what exactly is HTML5lib?
15:02
<jgraham>
cardona507: Is that a deep philosopical question or do you want a simple answer like "a set of implementations of the html5 parsing algorithm for various languages (principally python, also PHP, formerly ruby), and some associated utilities for working with HTML trees"
15:03
<cardona507>
jgraham - :) - not it isn't a philiosophical question - I actually am interested in what it is - thanks for the answer
15:03
<mikekelly>
is a form not considered a type of hyperlink?
15:06
<Philip`>
mikekelly: No - <a href> and <area href> and some <link href>s are the only hyperlinks
15:06
<Philip`>
http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#hyperlink-elements
15:08
<mikekelly>
Philip`: Ok - I was wondering more about the reason that distinction is held
15:09
<mikekelly>
i.e. a form links the UA to another URL .. seems like a hyperlink to me
15:10
<Philip`>
I'd guess it's because those are the only things that directly provide a URL for users to visit
15:10
<Philip`>
whereas form URLs aren't useful by themselves, since they require form data to be passed too
15:10
<Philip`>
(and lots of other URL attributes (<img src> etc) aren't followed by users)
15:11
<mikekelly>
so rel='search-result' wouldn't be an appropriate link relation for the google search box?
15:11
<mikekelly>
the link is variable
15:11
<mikekelly>
but it's constrained
15:11
<Philip`>
How would any consumer make use of that rel information?
15:12
<mikekelly>
the variable parts of a GET action are all search parts
15:12
<Philip`>
If the search form had rel="next" then what should happen in a UA which provides a 'next page' button in its UI based on rel=next links?
15:12
<mikekelly>
Philip`: a machine would be able to insert data into that form and understand the semantics of the resulting requesdt
15:14
<Philip`>
That wouldn't work on e.g. Google's search box because the semantics of the response depend on the parameters, e.g. if you click "I'm Feeling Lucky" then it sends different parameters and the result is a redirection to a result page instead of a list of results
15:15
<mikekelly>
what is the difference between those two submit buttons?
15:15
<mikekelly>
is that html?
15:18
<Philip`>
<form action=...><input type=submit name=btnG value=Search><input type=submit name=btnI value=Lucky></form>
15:18
<Philip`>
Oh dear
15:18
<Philip`>
If I click "I'm Feeling Lucky" with no text in the search box, it looks like an old Geocities page with fireworks everywhere :-(
15:19
<mikekelly>
er.. right
15:19
<mikekelly>
and that would be perfectly valid HTTP response
15:19
<mikekelly>
the redirect is a 'search-result'
15:19
<mikekelly>
a search result that redirects you..
15:19
<cardona507>
:-/ oh my - those google fireworks are nice
15:20
<Philip`>
They're terribly slow in Opera
15:20
<mikekelly>
Philip`: I don't see any problem with that at all.
15:20
<mikekelly>
infact, there is no problem with that at all
15:20
<daedb>
what fireworks?
15:20
<mikekelly>
take the URL that feeling luckky button generates
15:20
<mikekelly>
and put it in CURL
15:20
<Philip`>
Oh, they're much faster in Opera 10.50
15:20
<cardona507>
daedb - go to google and click i'm feeling lucky
15:21
<mikekelly>
and see what you get
15:21
<Philip`>
Hooray for faster Opera
15:21
<cardona507>
+1 to that!
15:21
Philip`
eagerly awaits one that's fast and also stable
15:22
<Philip`>
mikekelly: Do you think the rel should be a per-form thing, or a per-submit-button thing?
15:23
<mikekelly>
Philip`: per form..
15:23
<mikekelly>
the 'problem' you've identified doesn't exist
15:24
<daedb>
cardona507: I just get a page that explains the I'm feeling lucky function, no fireworks.
15:24
<cardona507>
daedb - I am logged in to my google account also - I don't know if that affects it - Philip`, are you logged in to your google account when you see the fireworks?
15:25
<Philip`>
mikekelly: It seems like a problem if the buttons do more differing things, or if you want to assign more specific semantics to the form, which don't seem like uncommon situations
15:25
<mikekelly>
Philip`: when you click I'm feeling Lucky - it's still making the resulting request to a search-result on google server
15:26
<Philip`>
mikekelly: (The specific case of search forms can be handled by <input type=search> anyway, so I'm assuming you want something more general)
15:26
<mikekelly>
so what can you actually change with an html form button?
15:26
<Philip`>
cardona507: I am both logged in and not logged in
15:26
<mikekelly>
all you can do is add another parameter to the search part of a URI
15:26
<daedb>
cardona507: I logged in... doesn't seem to make a difference
15:27
Philip`
goes away for a bit
15:27
<mikekelly>
Philip`: yeah something more general.. almost like.. a platform for development :)
15:27
<mikekelly>
*shock horror*
15:27
daedb
wants to see the fireworks too :(
15:30
<cardona507>
daedb - http://img85.imageshack.us/img85/7306/googlenewyear.png - enjoy :)
15:30
<cardona507>
just imagine that animated across the screen over and over
15:30
<mikekelly>
Philip`: I guess you could add in a more specific link relation for specific buttons..
15:32
<Huvet>
any clue about my question? how do I remove all HTML with html5lib?
15:32
<Huvet>
and second question, where did the documentation go?
15:33
<daedb>
oh, now I got it to work... had to click the "Google in english" link (but switching language in prefs did nothing) for it to work.
15:35
<Philip`>
Huvet: I'd guess it might be something like
15:35
<Philip`>
from lxml import etree
15:35
<Philip`>
parser = html5lib.html5parser.HTMLParser(tree = html5lib.treebuilders.getTreeBuilder('lxml'))
15:35
<Philip`>
doc = parser.parse(open(filename), encoding='utf-8')
15:35
<cardona507>
so google isn't showing those nice effects to our multilingual brothers and sisters - such a shame :)
15:36
<Philip`>
(untested)
15:36
<Philip`>
text = etree.tostring(doc, method='text')
15:36
<Philip`>
Huvet: and then escape all the "<"s and "&"s if you're going to display it in an HTML page
15:36
<Huvet>
ah, I'll try that, thanks
15:36
<Huvet>
I don't want any HTML at all
15:36
<Huvet>
just remove all the tags
15:37
<Huvet>
I just want to show the raw text content from a HTML page
15:38
<Huvet>
I guess you could mean that I still have to replace all < chars? Even though all HTML is removed?
15:38
<daedb>
cardona507: Maybe Google is just anti-Sweden, they're scared of our awesomeness :D
15:38
<cardona507>
:)
15:39
<Huvet>
<- fellow swede :)
15:39
cardona507
is feeling overwhelmed with awesomeness
15:40
<Philip`>
Huvet: Yeah, if the input is like "&lt;<b>foo&gt;" it should return "<foo>" etc - it's just extracting the text from the parsed document
18:33
<jwalden>
I'm sure I've read something about the preferred DOM for a block quote with an embedded authority (like "All the world's a stage<NL>-Shakespeare"), but I don't see any examples of it in the HTML5 spec for <blockquote> -- could anyone point me at what's the proper way?
18:36
<zcorpan>
"Content inside a blockquote must be quoted from another source" says the spec
18:37
<zcorpan>
so presumably <blockquote>All the world's a stage</blockquote><p>-Shakespeare</p>
18:39
<jwalden>
that would seem to treat -Shakespeare as semantically at the same level with any surrounding paragraphs of information, which doesn't seem right
18:43
<zcorpan>
hsivonen would probably do something like <blockquote>"All the world's a stage" -Shakespeare</blockquote>
18:46
<Philip`>
Use cite and point it at Shakespeare's FOAF file URI
18:46
<jwalden>
I was thinking of maybe doing <blockquote><p>All the world's a stage</p><p class="attribution">Shakespeare</p></blockquote> with some styling to right-align, "-"-prefix, etc.
18:46
<zcorpan>
anyone found any bugs with opera's <video> impl yet?
18:47
<zcorpan>
why use css to "-"-prefix?
18:47
<gsnedders>
<blockquote cite="http://en.wikipedia.org/wiki/As_You_Like_It">All the world's a stage<br>And all the men and women are merely players;<br>They have their exits and their entrances; And one man in his time plays many parts,<br>His acts being seven ages....</blockquote>
18:48
<AryehGregor>
Surely you mean "–"-prefix.\
18:48
<AryehGregor>
s/\\//
18:48
<gsnedders>
Then the browser can add the citation magically! :P
18:48
gsnedders
checks, and to his amazement actually quoted it correctly
18:49
<zcorpan>
AryehGregor: ?
18:49
<jwalden>
en dash versus hyphen
18:49
gsnedders
wonders why he can't type non-ASCII characters from this computer into irssi.
18:49
<AryehGregor>
Actually, an em dash might be best.
18:49
<gsnedders>
em dash, surely?
18:49
<gsnedders>
An en dash for that would be completely inappropriate
18:50
<jwalden>
wikipedia's dash article, strangely, doesn't suggest a "correct" dash there as far as I could tell
18:50
<Philip`>
gsnedders: That doesn't look right to me - surely you need a <br> before "And one"
18:50
<jwalden>
\2015 is the "quotation dash", but it's apparently used to *introduce* quotes, not to terminate them, from what I could tell
18:50
gsnedders
can't tell the difference between en and em dashes in this monospace font
18:50
<gsnedders>
Philip`: Ah, woops
18:50
<jwalden>
I had to /eval a copy-paste to determine code points :-)
18:51
<gsnedders>
jwalden: Yeah, it controls the spacing for it, as well as giving a slightly longer length than a em dash, IIRC
18:51
<Philip`>
gsnedders: Even I know that Shakespeare used narrow columns :-p
18:51
<gsnedders>
(the spacing is the most obviously different point to the em dash)
18:52
<Philip`>
gsnedders: Also, s/women are merely/women merely/ apparently
18:52
<Philip`>
gsnedders: You can't just get it wrong and then say you got it correct :-p
18:53
<gsnedders>
Yeah, definitely needed, otherwise it breaks from meter
18:54
<gsnedders>
Oh well, <q>The course of true love never did run smooth</q>.
18:54
gsnedders
hides
18:54
<jwalden>
http://www.cs.tut.fi/~jkorpela/html/bq.html is suggesting <bq/><div class>, abbreviating a bit
18:54
<gsnedders>
:P
18:54
<gsnedders>
Not <bq>!
18:55
<gsnedders>
bq is just _so_ HTML 3.
18:55
<zcorpan>
opera supports bq... i mean supported
18:55
<jwalden>
wait...was there actually a bq element? I was just avoiding the typing!
18:55
<gsnedders>
In HTML 3
18:55
<jwalden>
whaaa...
18:56
<gsnedders>
zcorpan: We still support it in the latest stable release, with our buggy implementation of HTMLQuoteElement!
18:56
<gsnedders>
(the only special attribute on HTMLQuoteElement over HTMLElement is cite, which should return an absolute URL, but returns the attribute value in O10.10 for blockquote and bq)
18:56
<zcorpan>
who cares about the latest stable release
18:56
<gsnedders>
(and in 10.50 doesn't exist on bq)
18:57
<gsnedders>
zcorpan: Me, as I had nothing to do with it, so any bugs in it aren't my fault, ever.
19:01
<Philip`>
zcorpan: Users? :-)
19:01
<Huvet>
Philip`: the html stripping code you proposed crashes on unicode characters I'm afraid
19:01
<zcorpan>
Philip`: yeah
19:01
<Huvet>
somewhere inside lxml.etree
19:02
<Huvet>
oh, hi zcorpan :)
19:02
<zcorpan>
hi Huvet
19:03
<gsnedders>
etree.tostring(Element, encoding=unicode, method='text', with_tail=False)
19:03
<Huvet>
thx
19:04
<jwalden>
aargh, <bq> plus <credit> in HTML3 are exactly the solution I desire for this; if only they'd been kept in later versions...
19:05
<zcorpan>
gsnedders: found any blog software with a serializer yet?
19:05
<gsnedders>
zcorpan: no
19:05
<zcorpan>
jwalden: we could add <credit> to html5--i mean html6
19:05
<gsnedders>
zcorpan: s/6//
19:05
<gsnedders>
:P
19:06
jwalden
wonders if there was a whatwg@ thread about it that he didn't read, probably given how many threads there have been on everything under the sun
19:06
<zcorpan>
html > html5
19:06
<jwalden>
I would be astounded if no one had ever mentioned it
19:07
<zcorpan>
hence,
19:07
<zcorpan>
> 5
19:07
<jwalden>
[EVAL-IN] "html" > "html5"
19:07
<jwalden>
[EVAL-OUT] false
19:07
<jwalden>
;-)
19:08
<gsnedders>
zcorpan: Why, you found any decent blog software?
19:08
<zcorpan>
no
19:09
gsnedders
really wants something sane for thereshouldbenored.com
19:10
<jwalden>
looks green to me!
19:10
<jwalden>
(after a handful of reloads)
19:12
<jwalden>
http://www.cs.tut.fi/~jkorpela/dashes.html suggests em dash for -Shakespeare
19:12
<zcorpan>
i'd like something for spacergif.mobi
19:12
<Huvet>
heh, that has got to be one of the worse domain names ever :)
19:13
<Huvet>
worst*
19:13
<Huvet>
I like it!
19:15
<gsnedders>
zcorpan: Hey, I at least have something at spacergif.mobi
19:15
jwalden
waits for the IF TLD so he can steal spacerg.if
19:15
gsnedders
still wants photos from the toilet there
19:15
<gsnedders>
(to make a joke very few will get)
19:16
<zcorpan>
gsnedders: what do you have at spacergif.mobi?
19:16
<zcorpan>
gsnedders: i have it on my phone
19:16
<gsnedders>
Oh, it's a gif
19:17
<gsnedders>
You could have something I could _see_!
19:17
<zcorpan>
you aint supposed to see spacer gifs
19:18
<gsnedders>
But there's no red, so I guess it passes.
19:18
<gsnedders>
jwalden: I'd never seen it green until a colleague sat around for a while reloading it.
19:18
<gsnedders>
zcorpan: What resolution?
19:19
<zcorpan>
gsnedders: blank is usually not a pass
19:19
<jwalden>
gsnedders: you still at opera, or back at school yet?
19:19
<gsnedders>
jwalden: At Opera
19:19
<zcorpan>
gsnedders: probably 640x480 or less
19:19
<gsnedders>
zcorpan: Or more to the point: can you read the sign?
19:19
<zcorpan>
yes
19:19
<gsnedders>
And see red?
19:19
<jwalden>
nice, must have been longer than the three-month periods I'm used to in the US
19:19
<zcorpan>
yes
19:20
<jwalden>
unless my sense of time is just shot
19:20
<gsnedders>
jwalden: Oh, I ended up staying on after internship for a gap year
19:20
<jwalden>
ah
19:22
<gsnedders>
But some people don't want me to leave at the end of my gap year
19:22
<gsnedders>
:P
19:22
<jwalden>
heh
19:23
<gsnedders>
(And I don't mean my father ;P)
19:23
<jwalden>
this is before college (I think), so I wouldn't recommend it, since I doubt you're planning to go to some sort of vocational/technical school
19:24
<gsnedders>
But education means exams, and exams suck. :P
19:25
<AryehGregor>
Tell me about it, I have my writtens in three days. >:(
19:26
<zcorpan>
gsnedders: it's 1200x1600 apparently
19:26
<jwalden>
I can take exams as an acceptable cost to pay for gaining the knowledge, mostly :-)
19:27
<gsnedders>
zcorpan: email it to me (me⊙gc)
19:28
<zcorpan>
wonder if i can email files with opera mini
19:33
<zcorpan>
hmm the <input type=file> control does nothing
19:37
<AryehGregor>
jwalden, the knowledge or the degree? You could always study by yourself and skip the exam bit if not for the "grades" part.
19:38
<AryehGregor>
Like just audit every course.
19:38
<AryehGregor>
Unless you can't bring yourself to study without exams.
19:39
<jwalden>
I'm not convinced you can learn as much just by self-study; doing it with others, struggling through it with them, is significant additional value
19:40
<Huvet>
gsnedders: thanks for that encoding attrib, works great :)
19:40
<gsnedders>
Huvet: That's literally what Anolis uses, so it should work
19:41
Huvet
googles Anolis
19:41
<Huvet>
ah, nice
19:41
<AryehGregor>
jwalden, you could go to college but just audit all your courses, and not take the tests. The only reason to actually take courses is if you want the degree.
19:42
<jwalden>
a degree's certainly a useful signaling mechanism
19:42
<AryehGregor>
Right, that's the key thing. You don't need exams to learn things, you need exams to prove to others that you've learned things.
19:42
<Huvet>
yeah, and don't forget the networking possibilities... lots of people get a job through their uni. network
19:43
gsnedders
got a job through #whatwg :P
19:43
<Huvet>
:)
19:45
<gsnedders>
http://krijnhoetmer.nl/irc-logs/whatwg/20081116#l-188
21:28
jgraham
notes that Shakespeare often deviates from meter
21:28
<jgraham>
I also note that I just pushed some changes to html5lib that should fix some stuff but probably doesn't because I have a cold
21:58
<gsnedders>
jgraham: So is taht 121
21:58
<gsnedders>
too?
21:58
<gsnedders>
Oh,y ou commented there
21:58
<gsnedders>
Just didn't close it