[17:40:22] anyone around yet? [18:40:14] trevor? are u there? [18:40:22] TrevorParscal: there? [18:43:21] ok [18:43:25] office meeting over [18:45:15] do you know if there is a negative letterspacing in the left navigation? [18:45:24] looks like if I rebuild it on ps [20:33:08] developers: looks the ntoc does not work in w3m. known bug? [20:38:29] What's w3m? [20:38:44] And what does "not work" mean in this context? The NTOC is half broken to begin with [20:40:47] RoanKattouw: is the bustedness something you're working on? anyway I can help out there? [20:46:10] Currently, when I'm not watching a movie, I'm working on some wrapping code for Nimish with a tricky DOM traversal algorithm [20:46:44] You can try to help with the NTOC brokenness if you want, it involves fixing context.fn.getSelection() [20:47:01] Which is supposed to move the selection in the iframe in evil browser-specific ways [20:49:26] I am not talking about prototype [20:50:13] Oh [20:50:25] Still, I never heard of w3m :) [20:50:38] is there production issues? [20:51:39] http://w3m.sourceforge.net/ [20:51:50] I don t use that myself [20:52:00] someone told me that vector does not work [20:53:04] nkomura: Apparently Vector, NTOC are broken in some obscure browser [20:53:07] TrevorParscal: ----^^ [20:53:26] i glanced at the link [20:53:38] it definelty os obscure [20:53:49] might be used by handicapped users....? [20:54:43] we have hard time keeping up even supporting major browser variance [20:55:20] so we are not in the position to work on an edge case at this moment [20:55:26] but if it is accessibility issue, [20:55:32] for handicap folks [20:55:40] i'd like to learn more about it [20:55:51] I have no idea - I just wanted to report that bug [20:58:44] apparently there was a fatality at Lille on the LGV. [20:58:52] I can't find anything about it on the internets [21:19:17] LGV? [21:22:15] Do you mean TGV or Eurostar? [22:05:15] RoanKattouw: do you know of any browser which the NTOC is currently functioning properly in? [22:06:56] Nope [22:07:05] Not the text moving thing at least [22:07:13] I wrote it for Firefox but it doesn't like it for some reason [22:09:39] yeah i'm wondering when it stopped working [22:09:53] not long ago it was still fine in FF [22:10:06] That would be before we started using the iframe, is my guess [22:10:20] Feel free to dive into it, I've got plenty of other tasks [22:10:31] it seems like most of the code is still operating on the textarea [22:10:44] Indirectly, it's not [22:11:00] The textSelection plugin is really weird right now, it'll pick the iframe over the textarea if it's there [22:11:10] so something like context.$textarea.textSelection will actually be run on the iframe? [22:11:20] Yes [22:11:23] haha [22:11:25] Only that function though [22:11:32] I know, it's totally crazy [22:11:37] not confusing code at all [22:11:44] We're meaning to rewrite that some day but we've got more urgent things to do [22:12:07] alright, we'll i'm diving through it trying to figure out where it's breaking [22:12:30] I think it's throwing an error in Firebug, should be a good starting point [22:14:06] i'm not seeing it [22:15:00] Have you clicked a section in the NTOC? [22:15:27] yes [22:15:56] Hm, looks like my code is not getting called, WTF [22:16:05] Jumping used to work [22:16:08] yeah it doesnt seem to make it into context.$textarea.textSelection [22:16:10] Just moving the cursor didn't [22:16:19] Well I'm off to bed now, so good luck :) [22:16:29] alright i'll keep playing around [23:16:04] TrevorParscal: ps, i note that there is serif vs sans-serif inconsistency on the different levels of content headers (and even between editsection spans) in the sandboxes (1 and 5 at least) [23:16:42] Yeah, I'm not involved in that work actually