| 00:24 | <zewt> | a "json working group"? |
| 01:04 | <GPHemsley> | are there things json is missing? |
| 01:05 | <hober> | technically the json rfc is informational; i guess a wg could re-publish it with no changes except to put it on the standards track. |
| 01:18 | <zewt> | doesn't seem like there are actually any problems to solve, heh |
| 01:46 | <GPHemsley> | Process sure is silly sometimes. |
| 07:06 | <annevk> | https://twitter.com/sgalineau/status/303641007151525888 hehe |
| 08:29 | <jgraham> | darobin: Just heard from the guy that wrote much of our DnD testsuite |
| 08:29 | darobin | can't help thinking he should roll some dice when it's put that way |
| 08:30 | <jgraham> | He described reorganising it to fit with the structure in the DND folder as "unrealistic" |
| 08:30 | <darobin> | with some justification, or just because? |
| 08:30 | <jgraham> | darobin: Indeed, roll 2 d20 and if they land you hit a bug in an implementation |
| 08:31 | <jgraham> | I think because of the sheer number of tests |
| 08:31 | <darobin> | mmmmm |
| 08:31 | <darobin> | lemme look |
| 08:32 | <darobin> | I see |
| 08:33 | <darobin> | jgraham: well, dnd is a rather coherent feature |
| 08:33 | <darobin> | I have no problem with its subsections being empty, and the whole TS being under html/editing/dnd/ |
| 08:33 | <darobin> | (with the subdirs from your friend) |
| 08:35 | <jgraham> | And leave the empty structure for people to use if they add new tests? |
| 08:37 | <jgraham> | In other news, I think that there must be some comedy mileage to get out of hsivonen being mistaken for a TAG member |
| 08:38 | <jgraham> | I'm just not sure what it is |
| 08:38 | <marcosc> | I don't know why hsivonen isn't a TAG member, really. |
| 08:38 | <marcosc> | (apart from his time having value :) ) |
| 08:39 | <marcosc> | Question: would it be a bad thing to attempt to describe a JSON structure using a WebIDL dictionary? |
| 08:39 | <jgraham> | Probably, yes |
| 08:41 | <marcosc> | The type conversion from WebIDL seems like a nice thing... I guess I could describe the structure using JSON schema, but I'm having NIH syndrome :) |
| 08:41 | <marcosc> | Otherwise, there is always that prose gibberish :) |
| 08:43 | <jgraham> | Well I guess if the JSON is sufficiently simple and regular it could work |
| 08:51 | <marcosc> | jgraham: it's mostly strings and a couple of numbers. I figure, then authors can have the freedom to write, for example: {"height": "200"} or {"height": 200} without being yelled at. |
| 08:53 | <marcosc> | dictionary{ unsinged short height; } could then handle the string to number conversion |
| 09:00 | <annevk> | https://www.google.co.uk/search?q=You+may+not+create+a+link+to+this+website+from+another+website+or+document+without+prior+written+consent&ie=UTF-8&oe=UTF-8&hl=en&client=safari&safe=on holy shit |
| 09:00 | <annevk> | people be crazy |
| 09:01 | <marcosc> | scary! |
| 09:02 | <marcosc> | We should link to all those sites :) |
| 09:17 | <a-ja> | <img longdesc="https://www.google.co.uk/search?q=You+may+not+create+a+link+to+this+website+from+another+website+or+document+without+prior+written+consent&ie=UTF-8&oe=UTF-8&hl=en&client=safari&safe=on"/>; |
| 09:24 | <marcosc> | a-ja, please don't link to that link, as they don't want you linking to google that contains the link to their site :P |
| 09:25 | <marcosc> | I hope google got prior written consent from all those people |
| 09:31 | a-ja | adds rel=nofollow |
| 09:52 | <annevk> | darobin: Editing requires a ton of research? I thought you already had a fulltime job? |
| 09:52 | <darobin> | annevk: my fulltime job is to make this whole pile of crap better |
| 09:53 | <darobin> | I focused a fair bit on testing over the past weeks, but now that there's tobie I can probably take on something extra |
| 09:53 | <annevk> | I'm just saying, fixing editing is a fulltime job by itself |
| 09:53 | <darobin> | yeah, I know it's a long-haul issue |
| 09:53 | <darobin> | but it's not like people are rushing in the volunteer |
| 09:53 | <darobin> | s/the/to/ |
| 09:54 | <darobin> | and it's a feature I care about |
| 09:54 | <Ms2ger> | It's mostly implementing now, isn't it? |
| 09:54 | <darobin> | there are still discrepancies |
| 09:54 | <darobin> | and they tend to be ugly |
| 09:54 | <darobin> | but Aryeh's done a great job moving it forward |
| 09:55 | <annevk> | Ms2ger: well and the wave of maintenance that creates, plus maybe adding new things? I haven't followed the work in detail at all though :( |
| 09:55 | <Ms2ger> | Sure |
| 09:56 | <Ms2ger> | But with nobody actively implementing, I don't think there's a whole lot of useful work to do on editing right now |
| 09:56 | <darobin> | actually the thread started because Microsoft is implementing |
| 09:56 | <annevk> | Is Alex still on the IE Team though? |
| 09:57 | <darobin> | "I am working on editing in IE, have issues of various scale" |
| 09:57 | <annevk> | heh oops |
| 09:57 | <annevk> | I guess he just stopped being chief layout |
| 09:58 | <darobin> | well as you said editing is a big chunk |
| 09:58 | <darobin> | so maybe he's chief editing now :) |
| 09:58 | <annevk> | Alex uses interesting email software |
| 09:58 | <annevk> | He emails to annevk⊙an, but inline it says ± From: annevankesteren⊙gc |
| 09:58 | <Ms2ger> | I thought he was smarter than letting someone make him chief editing ;) |
| 09:58 | <a-ja> | Scorecards! Get your scorecards... |
| 09:59 | <jgraham> | Isn't being made cheif of editing like being fired, but more subtle? |
| 09:59 | <annevk> | Ms2ger: looks like maybe you should define DocumentFragment.innerHTML after all |
| 09:59 | <Ms2ger> | Fun |
| 09:59 | <Ms2ger> | Let me know when Hixie's defined how it parses :) |
| 09:59 | <jgraham> | *chief |
| 10:00 | <annevk> | Ms2ger: at some point we should just merge domparsing into dom |
| 10:00 | <Ms2ger> | brb |
| 11:29 | <JibberJim> | Does Safari have a public bug repo? |
| 11:30 | <JibberJim> | I'm guessing not, got a video element bug on iOS and I suspect it's been raised as it's trivially obvious. |
| 11:30 | <darobin> | JibberJim: https://bugreport.apple.com/ |
| 11:31 | <darobin> | you won't like it though :) |
| 11:32 | <JibberJim> | yeah - non public though right... |
| 11:33 | <JibberJim> | If they want bug reports, showing the listed ones would be helpful. |
| 11:33 | <darobin> | well if they don't want to help you not submit dupes, it's their problem to sort that out |
| 11:34 | <darobin> | if it's a WebKit bug you can use the WebKit tracker, of course |
| 11:34 | <JibberJim> | Or I just won't submit it :) |
| 11:36 | <JibberJim> | javascript, cookies, apple id... recommend me use a browser I don't even have. |
| 11:37 | <darobin> | yeah, it's all a lovely process |
| 11:38 | <darobin> | you have iOS though, maybe it works on Mobile Safari |
| 11:38 | <darobin> | I'm sure it's a great experience |
| 11:39 | <annevk> | whoa, I'm in for two years on the TAG? |
| 11:44 | <darobin> | annevk: no, I think you're in for one year |
| 11:45 | <jgraham> | But don't worry you can always go for re-election! |
| 11:46 | <darobin> | actually there's an error on http://www.w3.org/2001/tag/ |
| 11:46 | <darobin> | all of the four horsemen are listed as having a two year term |
| 11:46 | <darobin> | but one of them got my seat, which was only up for one year |
| 12:17 | <annevk> | darobin: yeah, I was looking at that page |
| 12:18 | <darobin> | annevk: I reported the presumed bug, I'll let you know how long you'll actually spend in the salt mines |
| 12:47 | <annevk> | hsivonen: What in particular strikes me as weird is that we had Appendix C and that MIME type guidance document. And they utterly failed. And now there's Polyglot, which is more complex, and people expect it to succeed? |
| 12:51 | <darobin> | people expect polyglot to succeed? |
| 12:51 | <annevk> | Oh that thread is great. Jonas Sicking rallying for pouring resources into XHTML :-) |
| 12:54 | <annevk> | http://www.clinet.fi/~henris/ Ah, at one point hsivonen also used first-name-first-last-name-letter... |
| 13:01 | <MikeSmith> | Zach Kuznia implementing Streams API https://lists.webkit.org/pipermail/webkit-dev/2013-February/023928.html |
| 13:01 | <hsivonen> | I like brucel's lorem ipsum: <div>Bob Smith said at <a href="#permalink1">9.55 on 31 Febtember</a>: Can I use DRM in Polyglot documents?</div> |
| 13:02 | <hsivonen> | <div>Hixie said at <a href="#permalink2">9.57 on 1 June</a>: What's your use case?</div> |
| 13:04 | <Ms2ger> | Clearly those should be p's, though |
| 13:59 | <MikeSmith> | so I finally managed to get Servo to build but when I try to view the ../src/test/about-mozilla.html page I just get moji bake |
| 13:59 | <MikeSmith> | garbage text |
| 14:00 | <annevk> | MikeSmith: maybe ask in #developers on irc.mozilla.org? |
| 14:01 | <MikeSmith> | annevk: ok |
| 14:01 | <MikeSmith> | or actually I guess I should just complain in the #servo channel there |
| 14:01 | <annevk> | ah |
| 14:04 | <MikeSmith> | also never did manage to get mozjs to compile with clang. but maybe that's because I was pointing it at the clang from Chromium, and it detected that and failed on purpose |
| 14:05 | <MikeSmith> | is the format of Mozilla .manifest files documented somewhere? |
| 14:06 | <MikeSmith> | nm I'll ask on #developers |
| 14:17 | <annevk> | Hixie: you still want seamless <iframe> event thingies right? |
| 14:17 | annevk | takes another look at https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/shadow/index.html#event-retargeting |
| 14:44 | <annevk> | So how does http://trac.webkit.org/browser/trunk/Source/WebCore/dom/EventTarget.cpp#L150 walk the tree? |
| 14:49 | <annevk> | I guess that logic is in http://trac.webkit.org/browser/trunk/Source/WebCore/dom/EventDispatcher.cpp |
| 14:51 | <bijan> | Hi ho, I have an MSc student who's project is to independently implement the HTML5 parsing algorithm. We've gotten a bit confused by character reference tokenization. For data character references, such as: http://www.whatwg.org/specs/web-apps/current-work/multipage/tokenization.html#character-reference-in-data-state |
| 14:52 | <bijan> | The first step is to switch back to the Data state. |
| 14:52 | <bijan> | Whereas in attribute values switching back to the calling state is the last step: http://www.whatwg.org/specs/web-apps/current-work/multipage/tokenization.html#character-reference-in-attribute-value-state |
| 14:52 | <bijan> | Is this meaningful? We were having trouble making the machine work in the first case. |
| 14:53 | <bijan> | (I.e., since switching back to the data state seems to interrupt the reference consumption.) |
| 14:53 | <jgraham> | bijan: Switching states doesn't do anything until you return to the main loop |
| 14:54 | <bijan> | Is this documented somewhere per se? |
| 14:54 | <jgraham> | So you switch the state that will be used for processing when the tokenizer is next call, but proceed with the remainder of the steps in the current state |
| 14:54 | <bijan> | Why then the "finally" in the attribute value? |
| 14:55 | <bijan> | Yeah, that's the only thing that made sense, but the attribute value state suggested otherwise :) |
| 14:55 | <jgraham> | I don't know why the style is different in the two cases, but I don't think it's meaningful |
| 14:55 | <bijan> | Ok. Thanks. |
| 14:57 | <jgraham> | What kind of implementation are you doing (i.e. which language, will it be Open Source, etc.)? |
| 14:57 | <volkmar> | marcosc: the intent of your app: URI scheme spec is to have it integrated in the runtime spec or keep it outside of it? |
| 14:57 | <jgraham> | Oh well, I guess I'll never know |
| 15:02 | <annevk> | And http://trac.webkit.org/browser/trunk/Source/WebCore/dom/EventRetargeter.cpp#L75 seems to contain stuff now in the Shadow DOM spec... |
| 15:03 | <annevk> | bijan: feel free to file bugs on stylistic differences though |
| 15:03 | <darobin> | bijan: did you see jgraham's question before... oh damn |
| 15:06 | <jgraham> | Heh |
| 15:09 | <odinho> | bijan: Did you see jgraham's question? |
| 15:09 | <annevk> | And with "now" above I meant "not" |
| 15:09 | <annevk> | E.g. checking whether a node's an SVG element does not happen |
| 15:10 | <bijan> | I did, but my reply got eated: At the moment they are doing an initial prototype in Java to learn the algorithm. Then they'll select a language which doesn't have a native parser and supply one. |
| 15:10 | <bijan> | 15:04 |
| 15:10 | <bijan> | Open source, yes. I hope |
| 15:10 | <jgraham> | bijan: Cool |
| 15:10 | <odinho> | I know some people that'd be happy to get a nice one in C. :-) |
| 15:11 | <jgraham> | Yeah, the greatest benefit to humanity would be one written in C using the libxml2 infrastructure |
| 15:11 | <jgraham> | But of course the project might have different goals |
| 15:11 | <odinho> | Hububb didn't embed easily, and had too many errors, - python-html5lib worked very well, but was way too slow. |
| 15:12 | <odinho> | jgraham: Yeah, good point. Absolutely. |
| 15:12 | <marcosc> | volkmar, I don't mind |
| 15:12 | <marcosc> | mounir ^^ |
| 15:13 | <marcosc> | Having separate docs is easier for me to edit |
| 15:13 | <marcosc> | (they could then be all combined into one big mama doc) |
| 15:13 | <marcosc> | Less overhead when there are multiple editors, etc. |
| 15:17 | <bijan> | Well, C is a possibility, but the current leader is Smalltalk :) |
| 15:20 | <annevk> | bijan: no wonder people keep bringing up the university-industry mismatch :-) |
| 15:21 | <bijan> | Well, pedagogic reasons |
| 15:22 | <darobin> | JavaScript would be sweet :) |
| 15:22 | <jgraham> | darobin: Write it in C am emscripten will give you a js one for free :) |
| 15:22 | <jgraham> | *and |
| 15:23 | <darobin> | jgraham: how about write it in JS and asm.js will give you C speed free? :) |
| 15:23 | <jgraham> | (also, I think js has been done) |
| 15:23 | <darobin> | you're thinking of jsdom or another one? |
| 15:23 | <jgraham> | That's not really how asm.js works… |
| 15:23 | <mounir> | marcosc: I also prefer separated docs but it seems hard in that case to have app: making sense will fully separated from packaged apps definition |
| 15:23 | <darobin> | jgraham: I know, but a girl can dream right? |
| 15:24 | <jgraham> | It depends which girl, I guess? |
| 15:24 | <darobin> | not all girls dream of asm.js? |
| 15:24 | <jgraham> | annevk: Dude they are starting in Java. How much more "industry" can you get? |
| 15:24 | <darobin> | I thought I heard that 50 Shades of Grey made asm so popular and all |
| 15:25 | <annevk> | jgraham: hehe |
| 15:25 | <marcosc> | mounir: where do you see potential conflicts? |
| 15:25 | <darobin> | "prototyping in Java" — hadn't heard that one before :) |
| 15:26 | <jgraham> | A proper academic implementation would be in Coq and would be accompanied by a proof of correctness |
| 15:26 | <mounir> | marcosc: not conflicts just that "app:" scheme will be strongly liked with the app spec and the app spec with the "app:" scheme |
| 15:26 | <annevk> | http://trac.webkit.org/browser/trunk/Source/WebCore/dom/EventRetargeter.cpp#L41 o_O |
| 15:26 | <mounir> | marcosc: anyway, we will see, I would be fine with including the document in the behemoth spec and having the work being done separatedly and synchronized |
| 15:26 | <annevk> | Man this Shadow DOM code is full of hacks |
| 15:27 | <marcosc> | mounir: that sounds good. I can put in the appropriate hooks as we need to. |
| 15:27 | <mounir> | marcosc: will likely include the current version in my draft though if you don't mind (manually for the moment) |
| 15:28 | <marcosc> | mounir: not at all. Go for it :) |
| 15:32 | <bijan> | "prototyping in Java" —> the student knows Java but will have to get comfy with the target language |
| 15:32 | <darobin> | jgraham: re HTML parser in JS though, do you know which one you're thinking of? |
| 15:32 | <marcosc> | mounir: it would be nice if we could do the same thing with the manifest format and definition. I wouldn't mind spec'ing that part out. |
| 15:32 | <darobin> | because I don't believe that node-htmlparser is anywhere near the spec |
| 15:32 | <darobin> | and jsdom is flaky at best |
| 15:32 | <jgraham> | darobin: No, it was just a feeling |
| 15:32 | <darobin> | it does weird things with /> for instance |
| 15:33 | <darobin> | I don't think there's a compliant one |
| 15:33 | <jgraham> | Could have been one of those |
| 15:33 | <mounir> | marcosc: what do you want to change here? |
| 15:33 | <mounir> | we had a standalone spec for that in the past |
| 15:34 | <mounir> | but as we said in the mailing list, it's hard to make this independ |
| 15:34 | <marcosc> | mounir: want to lay out all the JSON members into their own sections. Want to add processing model. |
| 15:34 | <mounir> | independent from the rest of the spec |
| 15:34 | <mounir> | marcosc: processing model? |
| 15:34 | <marcosc> | mounir: you JSON.parse(), but then you need to do all type checking. |
| 15:35 | <marcosc> | like, what happens if "height": "200px" ? |
| 15:35 | <marcosc> | or height: " 200 " |
| 15:35 | <marcosc> | and so on |
| 15:36 | <marcosc> | mounir: there are also some funny things, like: "Icons must be square" |
| 15:37 | <marcosc> | :) |
| 15:37 | <mounir> | oh |
| 15:37 | <annevk> | don't be a square |
| 15:37 | <slightlyoff> | OH HAI annevk |
| 15:38 | <annevk> | hey hey |
| 15:38 | <slightlyoff> | sorry for being seemingly AWOL...detour on Future design...sigh |
| 15:38 | <annevk> | no worries, I'm sure it won't be a matter of days |
| 15:39 | marcosc | notes that the recent meteor in Russia was God's anger towards delays on DOMFuture |
| 15:40 | <sangwhan> | any sane reason to use eval() in favor of JSON.parse()? been trying to think of a good reason |
| 15:40 | <annevk> | sangwhan: only insane |
| 15:40 | <jgraham> | No |
| 15:40 | <sangwhan> | i'll go ahead and assume it's human stupidity |
| 15:45 | <sangwhan> | https://github.com/glow/glow1/blob/master/src/data/data.js#L356 |
| 15:46 | <zewt> | (really hoping this "futures" stuff doesn't end up in the platform; it's so ugly and unnecessary) |
| 15:47 | darobin | thought the meteor in Russia was God's anger with NavCon not being public yet |
| 15:47 | <MikeSmith> | haha |
| 15:47 | <zewt> | https://github.com/slightlyoff/DOMFuture/blob/master/reworked_APIs/WebCrytpo/example/after.html <- this is pretty horrifying |
| 15:48 | <slightlyoff> | zewt: I take it you saw the before? |
| 15:48 | <slightlyoff> | zewt: it's better |
| 15:48 | <slightlyoff> | there's no implicit end-of-turn oriented control flow |
| 15:49 | <darobin> | sangwhan: actually, at a quick scan, it's looking like that "glow" code (whatever that is) is using the old school JSON-regex trick |
| 15:49 | <zewt> | assumed "before" was just a traditional API, so didn't look at it |
| 15:49 | <darobin> | which is what was done for browsers that don't support JSON |
| 15:50 | <zewt> | yeah, that's just a regular event model, much more in line with the platform |
| 15:50 | <sangwhan> | darobin: i was just wondering why JSON.parse() isn't the default and that being the fallback |
| 15:50 | <darobin> | sangwhan: is it possible this was written a while ago? |
| 15:50 | <darobin> | without looking closely it looks like best practice from some years ago |
| 15:51 | <darobin> | there's a regex you can use on JSON to validate that it's sane, after which eval() is safe |
| 15:51 | <zewt> | darobin: not that it makes it feel safe |
| 15:51 | <zewt> | heh |
| 15:51 | <darobin> | so it might be old rather than stupid |
| 15:51 | <zewt> | (bruce schneier wouldn't be happy with me for saying that) |
| 15:52 | <sangwhan> | darobin: looks like the last update was 4 years ago |
| 15:53 | <darobin> | sangwhan: there you go |
| 15:53 | <zewt> | i've actually had to write JSON serializers in the last year :| |
| 15:53 | <zewt> | (in c#, iirc, for Unity) |
| 15:54 | <zewt> | seems strange to be in any environment today that doesn't provide it |
| 15:55 | <marcosc> | mounir: the problem with the way the current manifest side of things is written is that it mixes a lot (vendor specific) authoring requirements with the definition of the JSON members. |
| 15:55 | <zewt> | also I couldn't find any good, freely-licensed code to do it, which was even stranger (there were like 10 implementations I found, all of which er were either "no commercial use", gpl, or catastrophically bad code) |
| 15:57 | <mounir> | marcosc: any example? |
| 15:57 | <marcosc> | mounir: well, the MUST be square was one... there is also: |
| 15:58 | <marcosc> | stuff in there about length of names, and descriptions |
| 15:58 | <mounir> | marcosc: TBH, I have no idea if that's vendor specific |
| 15:59 | <mounir> | I took that part of the spec from anant who might have done it this way beacuse of our implementation (I really have no idea) |
| 15:59 | <mounir> | but I guess having some limits is a good thing |
| 15:59 | <marcosc> | mounir: I'm happy to check that stuff |
| 15:59 | <mounir> | saying "the description SHOULD NOT be too long" isn't ideal |
| 16:00 | <mounir> | putting a limit might help authors |
| 16:00 | <mounir> | though, we can also expect the UA to deal with long descriptions |
| 16:00 | <mounir> | I do not really care |
| 16:00 | <marcosc> | mounir: I'm mostly interested in runtime behaviour |
| 16:01 | <marcosc> | otherwise, we have a whole bunch of arbitrary enforcement points in the spec that shouldn't be there. Long descriptions should be trimmed down elsewhere (or there may be a valid reason for the long description). |
| 16:01 | <marcosc> | same with the name |
| 16:01 | <marcosc> | etc. |
| 16:02 | <marcosc> | mounir: it's kinda like saying in HTML, paragraphs SHOULD NOT be over 1000 characters |
| 16:03 | <marcosc> | reasonable, but o_O :) |
| 16:07 | <marcosc> | moj |
| 16:07 | <SimonSapin> | marcosc: 1000 is a bit small, but 640K ought to be enough for anybody |
| 16:07 | <marcosc> | exactly :) |
| 16:09 | <sangwhan> | i share that pain of not being able to find good, freely licensed code to do a certain thing, i had that problem with mersenne twister a while ago |
| 16:10 | <mounir> | marcosc: we need a ticketing system |
| 16:10 | <mounir> | I would gladly fix that |
| 16:10 | <marcosc> | mounir: I'd like to define the members of the manifest more like it's done in HTML. More like this (without the silly blue background, of course): http://jsbin.com/izewal/1/ |
| 16:11 | <mounir> | marcosc: and have another part defining the behaviour I guess |
| 16:11 | <marcosc> | right, or we can define the processing algorithms for each member as part of their definition. |
| 16:12 | <hsivonen> | bijan: unfortunately, the spec takes shortcuts with CDATA sections and entities. Splitting those into states is left as an exercise to the reader. |
| 16:13 | <marcosc> | mounir: like, with default_locale, there needs to be a check that the value is a valid language tag. |
| 16:16 | <marcosc> | mounir: regarding ticketing, we should just use GH issues |
| 16:18 | <mounir> | GH issues are terrible |
| 16:18 | <mounir> | I would prefer bugzilla |
| 16:19 | <mounir> | but I guess the group seems to be enclined to use GH |
| 16:19 | <jgraham> | I have no idea what you are talking about, but I concur that GH issues are terrible |
| 16:23 | <marcosc> | mounir, jgraham, I agree. There are some "limitations" :) |
| 16:23 | <marcosc> | some of which are easy to work around |
| 16:26 | <MikeSmith> | bugzilla sucks but GH issues sucks way more |
| 16:28 | <sangwhan> | GH issues is better than Google Code, although that doesn't say much |
| 16:30 | <MikeSmith> | rubbing two sticks together to make fire is better than Google Code |
| 16:30 | <sangwhan> | although haven't seen anything that's as pleasant to use as JIRA |
| 16:30 | <sangwhan> | one downside is that you possibly need a monster server to run it |
| 16:30 | marcosc | writes "Github issues VS Bugzilla" into his little book of religious wars. |
| 16:33 | <bijan> | hsivonen, thanks for the heads up. |
| 16:33 | <jgraham> | Woah, Jira and "pleasant to use" in the same sentence, without negation? |
| 16:33 | <karlcow> | "<darobin> without looking closely it looks like best practice from some years ago" hmmm Interesting statement to keep in mind. :) |
| 16:33 | jgraham | guesses sangwhan used eval() to parse JSON |
| 16:33 | <jgraham> | ;) |
| 16:33 | <jgraham> | *uses |
| 16:34 | <dglazkov> | good morning, WhatWg! |
| 16:34 | <darobin> | JIRA??? |
| 16:34 | <darobin> | hahahahahahahaha |
| 16:34 | sangwhan | likes JIRA |
| 16:34 | <slightlyoff> | howdy dglazkov |
| 16:35 | <darobin> | bugzilla could be okay if it weren't so slow |
| 16:35 | <darobin> | and a little CSS wouldn't hurt either |
| 16:36 | <sangwhan> | Bugzilla is nice too, but there are some annoyances when you try to customize the workflow |
| 16:36 | <jgraham> | I hate all issue trackers |
| 16:36 | <darobin> | you are very polite sangwhan |
| 16:36 | <darobin> | I'm with jgraham |
| 16:36 | <jgraham> | Or, at least, all the ones I have ever used |
| 16:36 | <sangwhan> | JIRA is a pain to customize (the admin ui is not that great) but you _can_ get it done |
| 16:36 | <sangwhan> | without having to hack the code, which becomes a massive pain to maintain later |
| 16:37 | <darobin> | issue trackers, mail clients, and a long list of other pieces of software that everyone seems to get wrong |
| 16:37 | <sangwhan> | there is only one true mail client, and it's alpine. i just happen to not use it. |
| 16:37 | <darobin> | all I recall from JIRA was the long list of bookmarklets I had just to work around its UI bugs |
| 16:38 | <karlcow> | the back of my bank statement envelop is my best issues tracker, though not practical for sharing with others. |
| 16:38 | <jgraham> | Jira really hates you changing issues. The default view is read-only, yhou have to go to a special "edit" page. Unless you want to make certain changes, which require a different page |
| 16:39 | <karlcow> | It is working also with electricity bills envelops |
| 16:39 | <jgraham> | At least in our rather old Jira |
| 16:39 | <sangwhan> | jgraham: sadly, that hasn't changed in JIRA 4 at least |
| 16:39 | <sangwhan> | jgraham: and yes, it's annoying. i don't notice it that much because i only comment and resolve :) |
| 16:40 | <jgraham> | Oh and the search UI is a <redacted> |
| 16:40 | <karlcow> | :) |
| 16:40 | <jgraham> | And it periodically forgets your search results |
| 16:40 | <jgraham> | and you can't search by URI |
| 16:41 | <sangwhan> | i don't think bugzilla's search ui is that much better though. |
| 16:41 | <marcosc> | mounir: any idea why the manifest format has "appcache_path"? Why not use the one in the HTML file? |
| 16:41 | <jgraham> | Or even by URL |
| 16:41 | <karlcow> | may I add the… <redacted> SOAP API for creating non browser clients. |
| 16:41 | <MikeSmith> | is Jira 4 the new BTS 3? |
| 16:41 | jgraham | should stop now |
| 16:41 | <sangwhan> | BTS3 = JIRA3 |
| 16:41 | <mounir> | marcosc: this is for hosted applications |
| 16:41 | <mounir> | so we can install the appcache data while installing the application |
| 16:41 | <mounir> | to give a better offline e |
| 16:41 | <mounir> | experience |
| 16:42 | <sangwhan> | JIRA4 i've dealt with in other projects (apache/skype/adobe uses it) |
| 16:42 | <mounir> | marcosc: we have plans to have a new appcache manifest in JSON and that would allow to have the full manifest description here (but that's not really a short term goal) |
| 16:43 | <marcosc> | mounir: I see |
| 16:43 | <sangwhan> | karlcow: i recall giving up with soap and parsing the html for my non-browser client :P |
| 16:43 | <karlcow> | heh |
| 16:43 | <darobin> | annevk: I can confirm that you're only on the TAG for one year |
| 16:44 | <darobin> | at the end of this year, I suggest you rerun with Henry on a Polyglot ticket |
| 16:44 | <marcosc> | heh |
| 16:44 | <mounir> | darobin: I've heard that the change of affiliation would have that effect anyway |
| 16:44 | <darobin> | mounir: huh? |
| 16:45 | <marcosc> | annevk's change of affiliation basically makes him a polyglot |
| 16:45 | <marcosc> | I think that is what mounir means |
| 16:46 | <MikeSmith> | sangwhan: wait Jira is not same BTS code that Jesper was working on for 25 years at Opera, right? He wrote it after he left |
| 16:47 | <mounir> | for me polyglot is someone speaking many languages, not sure about annevk ;) |
| 16:47 | <jgraham> | Maybe zcorpan should run on a polygot html/javascript ticket (see e.g. https://dvcs.w3.org/hg/webapps/file/0a4f622868eb/Workers/tests/submissions/Opera/constructors/Worker/AbstractWorker.onerror.html). Pretty sure slightlyoff would approve of the coming together of W3C/TC39 that would imply :) |
| 16:47 | <sangwhan> | MikeSmith: I have my suspicions that code is now with the same company that wrote JIRA, but possibly not in the form of JIRA. |
| 16:48 | <sangwhan> | http://software.intel.com/en-us/articles/technical-reference-intel-html5-app-porter-tool-beta |
| 16:48 | <sangwhan> | Interesting idea, probably wouldn't use it myself |
| 16:52 | <MikeSmith> | sangwhan: the best feature of the html5 tool is the part where it converts Xcode projects in Visual Studio projects |
| 16:52 | <slightlyoff> | jgraham: I enjoy that you put real work into trolling. zewt just tells you that new stuff isn't what he's used to...you really sink your teeth into it. |
| 16:52 | <sangwhan> | MikeSmith: because who wouldn't love to write HTML in visual studio |
| 16:54 | <slightlyoff> | sangwhan: actually...it's quite good for that these days. |
| 16:55 | <bijan> | Hmm. Are these documents really polyglot or are they expressed in a pidgin. |
| 16:55 | <marcosc> | MikeSmith: I knew a dude that did that. All the Opera standards support docs were done that way :) |
| 16:55 | <jgraham> | That counts as trolling now? Either internet standards are slipping or I badly need to recalibrate my "lighthearted satire" mode. |
| 16:55 | <sangwhan> | slightlyoff: I still have to use VS2005/VS2008, as the EVC compiler was nuked in 2010+ |
| 16:56 | <bijan> | Polyglot applies to people, right? I.e., multilingual speakers that speak more than 3 languages (typically) |
| 16:56 | <slightlyoff> | you can side-by-side that, right? |
| 16:56 | <sangwhan> | if you have a license, yes :) |
| 16:56 | <marcosc> | bijan: sure. But that sense of the word is no fun to make fun of. |
| 16:56 | sangwhan | is a stone age caveman, still uses textmate 1 for any html/css/js code |
| 16:57 | <bijan> | I guess "Pidgin XHTML" doesn't sound so very cool. |
| 16:58 | <marcosc> | heh, that sounds way better than polyglot! |
| 16:58 | bijan | wonders who miscoined it and if they regret polluting the meaning |
| 16:58 | <marcosc> | a polyglot sounds like something I would chew to throw a math teacher |
| 16:59 | sangwhan | is looking at vs2012 in the meanwhile, just not to be biased |
| 16:59 | <bijan> | That's a "polysnot", i.e., what your parrot sneezed on you |
| 16:59 | <jgraham> | Surely if you take a pigin and make a standard, it become a creole? |
| 16:59 | <marcosc> | :) |
| 17:00 | marcosc | slowly backs away from this now... |
| 17:00 | <sangwhan> | http://www.microsoft.com/visualstudio/eng/ is a blank page in Opera(Presto). Joy. |
| 17:00 | <bijan> | Hmm. I guess. But I thought creoles were independent languages |
| 17:00 | <bijan> | "Polyglot" HTML is always parasitic on the parent languages |
| 17:01 | <jgraham> | I guess |
| 17:01 | <jgraham> | But once you have a standard you have "native speakers" |
| 17:01 | <bijan> | I guess if people "speak it" nativity then it's a creole |
| 17:01 | <bijan> | But that could happen pre standard |
| 17:01 | <darobin> | now let's round up this discussion of language variations by digging into how to capture their media types properly |
| 17:02 | <bijan> | text/html+pidginxml |
| 17:02 | <darobin> | I like that one |
| 17:02 | <darobin> | text/html+pidginxml;version=whatwg-creole works too |
| 17:03 | <darobin> | (I forgot I also wanted to bring version indicators into the chat) |
| 17:04 | <bijan> | Interesting, polyglot documents suggest use of non-polyglot parsers |
| 17:04 | <MikeSmith> | polyglot is an elaborate troll conceived by the TAG consigliere in collusion with a faction within the HTML WG chairs |
| 17:04 | <Ms2ger> | There are no polyglot parsers |
| 17:04 | <bijan> | I.e., either HTML5 native or XTHML5/XML based parsers, but not something that could consume either |
| 17:05 | <Ms2ger> | And that's my limit of one sentence about polyglot a week |
| 17:05 | <bijan> | Sure there are, at least easily bolted together |
| 17:05 | <bijan> | Depends on where you put the parser boundary :) |
| 17:15 | <MikeSmith> | somebody needs to provide the punchline for dude's "Many sites use conneg to treat mobile as a completely separate problem" comment |
| 17:17 | <MikeSmith> | "I develop for the long haul, not what works best today" |
| 17:18 | <MikeSmith> | I think that proves this guy in on the troll |
| 17:32 | <karlcow> | ahaha |
| 17:32 | <karlcow> | first reference on w3c mailing list with regards to html is made by… drum… hixie. |
| 17:32 | <karlcow> | http://lists.w3.org/Archives/Public/public-html/2008Aug/0301.html |
| 17:33 | <karlcow> | We could, if people really want to continue the ridiculous practice of |
| 17:33 | <karlcow> | writing polyglot documents, allow lang="" in HTML documents, thus |
| 17:33 | <karlcow> | providing a conforming way to set the language that is allowed in both |
| 17:33 | <karlcow> | forms. |
| 17:33 | <karlcow> | Date: Tue, 12 Aug 2008 10:12:39 +0000 (UTC) |
| 17:35 | <Ms2ger> | zewt, so did you write a high-quality, freely licensed JSON serializer library for C#? ;) |
| 17:42 | <zewt> | Ms2ger: unfortunately I needed it for work, so it was only one of those things |
| 17:42 | <Ms2ger> | "for C#"? ;) |
| 17:43 | <zewt> | i will destroy you |
| 17:46 | <Ms2ger> | In case people haven't heard where Sylvain is going and have member access: http://www.w3.org/mid/3C4041FF83E1E04A986B6DC50F0178291BF6E264⊙Trcmc |
| 18:39 | <annevk> | hober: sudo make me sando |
| 18:39 | <annevk> | hober: sounds weird |
| 18:42 | <Ms2ger> | OH: "W3C Invites Implementations of Turtle" |
| 18:42 | <wilhelm> | Is that some semantic web thing? |
| 18:44 | <Philip`> | It's one of the myriad serialisations of RDF |
| 18:45 | <charl_> | i have actually never seen it implemented personally |
| 18:46 | <charl_> | oh wait, this is a new one, i was thinking of another serialisation |
| 18:46 | <charl_> | found it: n-triples |
| 18:46 | <Ms2ger> | Aren't those just tuples? |
| 18:47 | <wilhelm> | I've actually come into contact with RDF on a real project for the first time. It's even more horrible than I had imagined. |
| 18:47 | <Ms2ger> | My condolences |
| 18:48 | <charl_> | ah, n-triples is a subset of turtle indeed |
| 18:50 | <marcosc> | I'm going to punch darobin for every time I have to write a <section> tag because of stupid Respec.js. |
| 18:51 | sangwhan | noticed that WebGL 1.0.2 ratification started, and of course non-khronos members aren't even allowed to see it |
| 18:52 | <charl_> | no wait, i was wrong again, i was thinking of notation3 :D |
| 18:52 | <charl_> | forgot what it was called; was way too long ago |
| 18:53 | <marcosc> | mounir: oh crap. I was working off the samsung document :{ |
| 18:53 | <marcosc> | I fixed a bunch of typos |
| 18:54 | <mounir> | marcosc: sorry for you :) |
| 18:54 | <mounir> | marcosc: though, we still don't know what is going to be the FPWD |
| 18:54 | <mounir> | I genuinly not understood what their email about our proposal "merge" was trying to say |
| 18:55 | <marcosc> | mounir: I read it as "we took your stuff and built onto of it ... and took out the bits we didn't quite agree with" |
| 18:55 | <marcosc> | mounir: too many chefs in the kitchen |
| 18:58 | <marcosc> | mounir: I've mostly rewritten the manifest props descriptions. Will you consider it for integration. |
| 18:58 | <marcosc> | ? |
| 18:59 | <marcosc> | It will take me a few more days to complete it. But it will make the manifest part of the document easier to implement. |
| 19:02 | <mounir> | marcosc: do you have a preview? |
| 19:02 | <marcosc> | early preview: http://jsbin.com/enohit/1/edit |
| 19:05 | <mounir> | marcosc: feel free to do a pull request when you are done (on my github fork) |
| 19:05 | <marcosc> | mounir: I've fixed up some of the textual descriptions, and started describing the structure of the manifest in terms of object types where it is appropriate. Then those objects can be processed accordingly. Have not started on any of the processing stuff yet. |
| 19:05 | <marcosc> | ok, will do. |
| 19:07 | <marcosc> | mounir: also, can we change application/x-web-app-manifest+json to application/webapp-manifest+json ? |
| 19:07 | <marcosc> | If this is going to be the "real deal" we can drop the x-, and the "web-app" is ugly. |
| 19:15 | <mounir> | marcosc: I would prefer this to be asked in the mailing list but I have nothing against |
| 19:17 | <marcosc> | mounir: ok, np. |
| 19:28 | <tantek> | application/webapp-* does seem redundant |
| 19:29 | <tantek> | marcosc do you mean something like application/manifest+json ? |
| 20:04 | <tobie> | marcosc: you know I added a markdown mode to ReSpec, right. Wouldn't want darobin hurt. |
| 20:11 | <karlcow> | arf |
| 20:13 | <miketaylr> | moo |
| 20:39 | <wilhelm> | marcosc: Thanks fot the kind words. After it was retweeted by some journalists, I was a little worried I was too open. I still love that little browser vendor, despite my disappointment. (c; |
| 20:39 | <wilhelm> | s/fot/for |
| 21:07 | <jamesr> | tantek, you there? |
| 21:07 | <jamesr> | or anyone who knows 'bout fullscreen? |
| 21:34 | <karlcow> | http://blog.python.org/2013/02/announcing-defusedxml-fixes-for-xml.html |
| 21:57 | <SimonSapin> | Nice! http://w3cmemes.tumblr.com/post/43499115162/simon-sapin-laughs-at-your-weak-timid-requests |
| 22:05 | <TabAtkins> | SimonSapin: Hahaha |