fluid-work IRC Logs-2011-12-09

[08:23:16 CST(-0600)] <cindyli> anastasiac: i noticed a bug with css probably that when UIO "line spacing" gets increased, the size of "log out" button gets enlarged but not "show/hide display preferences"

[08:53:47 CST(-0600)] <anastasiac> cindyli, thanks for catching that - could you file a JIRA for it?

[09:14:55 CST(-0600)] <cindyli> anastasiac: i've fired a jira for the "show/hide display preferences" button size issue - http://issues.fluidproject.org/browse/STUDIO-19

[09:16:07 CST(-0600)] <cindyli> anastasiac: in chrome and safari, there's a gap in btw the "show/hide display preferences" button and the top blue line. I've filed another jira for it - http://issues.fluidproject.org/browse/STUDIO-20

[09:16:21 CST(-0600)] <anastasiac> thanks, cindyli

[09:16:26 CST(-0600)] <cindyli> np, anastasiac

[09:18:07 CST(-0600)] <anastasiac> cindyli and michelled, I've modified the JIRA settings for the Studios project so that we now have the same workflow as Fluid. This means we can set the workflow state to "needs commit" for issues that have an outstanding pull request. This is helpful for knowing what the status of things are. It's also helpful if you're working on something to assign it to yourself and set the status to 'in progress'. That way, when we're looking to see what to work

[09:18:07 CST(-0600)] <anastasiac> next, it's easy to know what's already being worked on

[09:19:10 CST(-0600)] <cindyli> thanks, anastasiac, i will do

[09:19:39 CST(-0600)] <cindyli> that's the thing i normally ignore :-P

[09:28:37 CST(-0600)] <michelled> cindyli: do you have any pull requests that are almost ready?

[09:28:51 CST(-0600)] <michelled> I'm thinking jumpy UIO and broken tags pages

[09:28:55 CST(-0600)] <cindyli> yes, STUDIO-10 in a couple of mins

[09:29:21 CST(-0600)] <cindyli> STUDIO-10 is for the broken tags page, michelled

[09:34:22 CST(-0600)] <colinclark> michelled: I'm looking at your STUDIO-11 pull request

[09:34:28 CST(-0600)] <colinclark> can you explain really quick how I can verify the fix?

[09:35:51 CST(-0600)] <michelled> colinclark: click on a tag and you'll go to a page with a similar look to the first page

[09:36:58 CST(-0600)] <michelled> there should not be a space between an entry's summary and the tags for the entry

[09:37:14 CST(-0600)] <cindyli> michelled: regarding the jumpy UIO, which approach we're going to take? 1) merge antranig's pull request of refactored UIO into infusion, after he integrates the "shadow" branch into the pull request. 2) fluid studios uses its own infusion development version which is a copy of Antranig's "shadow" branch

[09:37:39 CST(-0600)] <michelled> cindyli: that's a great question

[09:37:46 CST(-0600)] <michelled> we should probably do 1)

[09:37:58 CST(-0600)] <michelled> we can probably live with jumpy UIO until we get it integrated

[09:38:15 CST(-0600)] <cindyli> ok, michelled

[09:38:16 CST(-0600)] <cindyli> michelled: i just submitted a pull request for STUDIO-10 - https://github.com/fluid-project/studios.fluidproject.org/pull/20

[09:38:22 CST(-0600)] <michelled> thanks!

[09:38:24 CST(-0600)] <cindyli> np

[09:40:19 CST(-0600)] <cindyli> anastasiac, michelled, any jira off the top of your head that you want me to work on? otherwise, i will scan thru the jiras and pick one myself.

[09:40:23 CST(-0600)] <michelled> cindyli: I love it that the fix involves removing about 20 characters

[09:40:41 CST(-0600)] <cindyli> agree, it's lovely

[09:42:43 CST(-0600)] <michelled> cindyli: probably one of the IE ones would be good

[09:43:05 CST(-0600)] <cindyli> michelled: jira#?

[09:43:28 CST(-0600)] <michelled> I guess 8 if more important than 7 so STUDIO-14

[09:43:39 CST(-0600)] <cindyli> ok, michelled

[09:47:35 CST(-0600)] <cindyli> michelled, anastasiac, during the process of fixing STUDIO-10, I actually found that the number of postings being displayed on the front page and the archive page is controlled by the admin "reading" setting. The action in the backend script that's intended to apply different numbers on the two pages without considering this setting would cause problem. The point I wanna bring up is that, right now, this default value is set to 10, but we probably want a

[09:48:27 CST(-0600)] <anastasiac> good point, cindyli. If it's set to 10, why in only one showing up on the archive page?

[09:48:31 CST(-0600)] <michelled> jvass: perhaps you can weigh in on what that setting should be

[09:49:09 CST(-0600)] <cindyli> anastasiac: that's because our archive.php was trying to retrieve one at a time

[09:49:27 CST(-0600)] <anastasiac> ah, ok, so you're fixing that?

[09:49:39 CST(-0600)] <cindyli> anastasiac: ya, i've sent a pull request for that

[09:49:47 CST(-0600)] <anastasiac> thanks

[09:49:50 CST(-0600)] <cindyli> np

[09:51:43 CST(-0600)] <michelled> anastasiac: should I be expecting an update to your pull request soon?

[09:52:03 CST(-0600)] <anastasiac> yes, michelled, just checking across browsers now

[09:52:14 CST(-0600)] <michelled> great

[09:54:04 CST(-0600)] <anastasiac> michelled, changes pushed to my branch, they should be part of the request now

[10:03:15 CST(-0600)] <michelled> colinclark: I've dealt with several pull requests this morning - you probably need to do a pull

[10:03:37 CST(-0600)] <colinclark> I'm a git mess this morning

[10:04:24 CST(-0600)] <michelled> can I help at all?

[10:06:38 CST(-0600)] <michelled> jameswy, jvass: the studios dev site is updated with our latest fixes. you might want to take a peek: http://dev.studios.fluidproject.org/

[10:13:04 CST(-0600)] <colinclark> michelled: I've pushed your STUDIO-11 fix

[10:13:16 CST(-0600)] <michelled> thx colinclark

[10:13:22 CST(-0600)] <colinclark> Remind me what I should do next in terms of our JIRA workflow

[10:13:26 CST(-0600)] <colinclark> Do I resolve it?

[10:13:29 CST(-0600)] <colinclark> I commented on the JIRA

[10:13:43 CST(-0600)] <michelled> yes, resolve it

[10:15:24 CST(-0600)] <colinclark> michelled: Done

[10:31:01 CST(-0600)] <colinclark> We're standing up?

[11:03:29 CST(-0600)] <michelled> anastasiac, cindyli: I think we have some refinements on the theme to do - currently using the rich text editor it looks I can get bullets to show up in my post but we strip that out in our theme

[11:04:05 CST(-0600)] <michelled> I've started to put Tona's write up on the video player onto the dev site http://dev.studios.fluidproject.org/?p=1

[11:49:40 CST(-0600)] <Bosmon> Hi cindyli - I am glad that the horrible jumping story is at an end

[11:49:58 CST(-0600)] <cindyli> yay!!

[11:52:28 CST(-0600)] <Bosmon> I guess it is a very peculiar choice in HTML for iframes to have an "inline" display by default

[11:53:17 CST(-0600)] <Bosmon> And also, it is unclear what exactly in the other contexts led the iframe to end up with display "block"... I spent several hours in the DOM debugger until I hit upon the right point, since this doesn't actually show up clearly in the element's properties

[12:52:53 CST(-0600)] <colinclark> I'm doing some testing of the Studios site with NVDA

[12:53:03 CST(-0600)] <colinclark> There are lots of really excellent things with the site

[12:53:12 CST(-0600)] <colinclark> Really good link descriptions

[12:53:29 CST(-0600)] <colinclark> Some nice landmarks that differentiate "complementary" content from the main content

[12:53:40 CST(-0600)] <colinclark> As a viewer, the experience is really excellent

[12:53:50 CST(-0600)] <colinclark> With the exception, I'm afraid to admit, of UIO

[12:54:08 CST(-0600)] <colinclark> Which seems to lack, in some cases, labels for some controls

[12:55:13 CST(-0600)] <colinclark> No indication of what the "Show Display Preferences" button actually does

[12:56:29 CST(-0600)] <colinclark> The Text Size and Line Spacing slider handles are both just read as "Slider 1"

[12:56:40 CST(-0600)] <colinclark> That might be due to the cursor mode, I'll have to check

[12:56:44 CST(-0600)] <colinclark> Otherwise, pretty decent

[12:57:09 CST(-0600)] <colinclark> The table of contents feature seems to break the alignment of the Log In and Show Display Preferences button when it's turned on

[12:57:13 CST(-0600)] <colinclark> hopefully that's a pretty easy fix

[13:14:52 CST(-0600)] <michelled> cindyli: are you busy at the moment?

[13:15:08 CST(-0600)] <cindyli> michelled: working on STDIO-14. what's up

[13:15:53 CST(-0600)] <michelled> with some brief testing it seems that the editor in wordpress is not accessible

[13:16:18 CST(-0600)] <michelled> can you start to do some digging to see if you can find one that is?

[13:16:29 CST(-0600)] <michelled> perhaps there's a wordpress plugin?

[13:16:33 CST(-0600)] <cindyli> ok, michelled

[13:22:56 CST(-0600)] <michelled> cindyli: any luck yet?

[13:24:05 CST(-0600)] <cindyli> michelled: wordpress uses tinymce editor, which should be pretty good with accessibility. i'm trying to figure out how to nav around the toolbars and editor with my MAC keyboard, which doesn't have ALT key

[13:25:10 CST(-0600)] <michelled> cindyli: can you try the dev site with you windows machine?

[13:25:20 CST(-0600)] <cindyli> sure, michelled

[13:54:05 CST(-0600)] <cindyli> michelled: i need a login to dev studio to access the page with editor

[14:26:21 CST(-0600)] <cindyli> michelled: none of the shortcut keys specified in tinymce accessibility page works - http://www.tinymce.com/tryit/accessibility.php

[14:26:38 CST(-0600)] <cindyli> neither in the context of wordpress

[14:26:55 CST(-0600)] <michelled> cindyli: try using 'control' as the modifier key

[14:27:15 CST(-0600)] <cindyli> michelled: tried, no luck, even with windows ALT

[14:27:52 CST(-0600)] <michelled> also, jameswy mentioned that the 'fn' key plus the 'option' key is generally the same as 'alt'

[14:28:04 CST(-0600)] <cindyli> ok, trying

[14:29:08 CST(-0600)] <cindyli> no, don't work

[14:30:07 CST(-0600)] <cindyli> i will see if there's another editor that can be easily plug into wordpress and with a better accessibility support, michelled

[14:41:55 CST(-0600)] <cindyli> michelled, anastasiac, i'm going to implement the CKEditor plugin to replace tinymce. CKEditor apparently has a better accessibility support at least. Any of you has any reason/experience that could stop this switch?

[14:43:45 CST(-0600)] <michelled> I think it's a great experiment cindyli

[14:43:53 CST(-0600)] <michelled> let us know how it goes

[14:43:57 CST(-0600)] <cindyli> sure

[14:53:29 CST(-0600)] <sgwcollins12> hello

[14:55:13 CST(-0600)] <cindyli> michelled: CKEditor looks and works great. you will have to install the plugin yourself with the download from http://wordpress.org/extend/plugins/ckeditor-for-wordpress/ because the plugin installation inserts data into db so a sole script pull-out from git would not work without the db data

[14:56:06 CST(-0600)] <michelled> ok cindyli thx

[14:56:21 CST(-0600)] <cindyli> np

[15:00:01 CST(-0600)] <sgwcollins12> hey guys I have a question about the fluid infusion color and contrast is it suppose to work the exact same when the background is an image?

[15:13:31 CST(-0600)] <anastasiac> cindyli: http://issues.fluidproject.org/browse/STUDIO-24

[15:13:37 CST(-0600)] <anastasiac> michelled: http://issues.fluidproject.org/browse/STUDIO-23

[15:13:52 CST(-0600)] <cindyli> thanks, anastasiac

[15:21:05 CST(-0600)] <colinclark> cindyli: Do you think it would be very hard to put a label into the Add New Posts page for the title edit field?

[15:21:11 CST(-0600)] <colinclark> It appears not to have one

[15:21:23 CST(-0600)] <colinclark> I assume there are just PHP pages for each of these things that we might be able to customize?

[15:21:39 CST(-0600)] <cindyli> colinclark: should be simple

[15:25:21 CST(-0600)] <cindyli> colinclark: there is already a <label> element there that's associated with the title edit field

[15:25:28 CST(-0600)] <colinclark> gmm

[15:25:37 CST(-0600)] <colinclark> What's its label?

[15:25:41 CST(-0600)] <cindyli> hope we are looking at the same page

[15:25:49 CST(-0600)] <cindyli> enter title here

[15:27:06 CST(-0600)] <colinclark> I think we are, yes

[15:27:12 CST(-0600)] <colinclark> Could be user error on my part

[15:27:15 CST(-0600)] <colinclark> let me have a closer look

[15:27:22 CST(-0600)] <colinclark> Or rather, listen

[15:34:40 CST(-0600)] <colinclark> Okay, so cindyli and michelled

[15:35:03 CST(-0600)] <colinclark> The user experience for the rich text editor in WP is mind-boggling

[15:35:09 CST(-0600)] <colinclark> It's so patchy

[15:35:27 CST(-0600)] <colinclark> So this particular version of TinyMCE has some decent support for screen readers

[15:35:46 CST(-0600)] <colinclark> In NVDA, when I get focus in the rich text control, I'm told how to access the tool bar, and how to access the help

[15:36:02 CST(-0600)] <colinclark> The toolbar is represented as a desktop-style toolbar interaction

[15:36:05 CST(-0600)] <colinclark> which makes some sense

[15:36:08 CST(-0600)] <colinclark> good labels, etc.

[15:36:15 CST(-0600)] <colinclark> Help is very helpful

[15:36:21 CST(-0600)] <colinclark> describes various accessibility features

[15:36:22 CST(-0600)] <colinclark> BUT

[15:36:28 CST(-0600)] <colinclark> it's presented inside a modal dialog

[15:36:34 CST(-0600)] <colinclark> which appears to have no controls for closing the help

[15:36:42 CST(-0600)] <cindyli> did you try ESC

[15:36:49 CST(-0600)] <colinclark> and, like many other modal dialogs we've met on the web, allows me to tab right out of it

[15:37:04 CST(-0600)] <colinclark> cindy, yes, esc works

[15:37:10 CST(-0600)] <colinclark> And is reasonably sensible

[15:37:33 CST(-0600)] <colinclark> I'm almost tempted to just provide some visible keyboard instructions

[15:37:39 CST(-0600)] <colinclark> like we do with the Reorderer

[15:37:40 CST(-0600)] <colinclark> and move on

[15:39:27 CST(-0600)] <cindyli> great review, colinclark

[15:39:50 CST(-0600)] <colinclark> I still haven't figured out how to escape from the editor

[15:39:58 CST(-0600)] <colinclark> but if they've put all this work into it, there must be a way

[15:40:06 CST(-0600)] <colinclark> cindyli: Should I check the TinyMCE documentation?

[15:40:28 CST(-0600)] <cindyli> what do you mean to escape from the editor

[15:40:32 CST(-0600)] <cindyli> tab out of it?

[15:40:34 CST(-0600)] <colinclark> yep

[15:40:35 CST(-0600)] <colinclark> exactly

[15:40:41 CST(-0600)] <colinclark> Focus is trapped in the editor

[15:40:42 CST(-0600)] <cindyli> you cannot tab out of it?

[15:40:44 CST(-0600)] <colinclark> no

[15:40:53 CST(-0600)] <cindyli> interesting. let me try

[15:41:00 CST(-0600)] <colinclark> Our version of WP uses TinyMCE 3.4.2, btw

[15:41:02 CST(-0600)] <colinclark> in case it helps

[15:41:17 CST(-0600)] <cindyli> btw, i also prefer to go with wordpress default editor

[15:41:24 CST(-0600)] <colinclark> ok

[15:41:32 CST(-0600)] <cindyli> which may have more support

[15:41:37 CST(-0600)] <colinclark> So the other thing we'd need to do...

[15:41:46 CST(-0600)] <colinclark> is to draw good focus outlines in the toolbar

[15:41:57 CST(-0600)] <colinclark> I'd hope we might be able to do that with some strategic use of the :focus pseudoselector

[15:41:59 CST(-0600)] <colinclark> But I don't know

[15:42:09 CST(-0600)] <colinclark> michelled: Probably it's worth getting your thoughts on this

[15:42:14 CST(-0600)] <colinclark> If you want, I can show you my experience

[15:42:19 CST(-0600)] <colinclark> Would you guys like to hear it with NVDA?

[15:42:22 CST(-0600)] <colinclark> and then assess?

[15:44:01 CST(-0600)] <michelled> sure colinclark

[15:54:22 CST(-0600)] <anastasiac> michelled and cindyli: I've pushed a start at the WP admin focus styling to my github, in the STUDIO-25-wp-focus-styling branch. I've commented on the JIRA as well.

[16:06:17 CST(-0600)] <cindyli> colinclark, michelled, found this about how to get out of tinymce editor - "An adaptive technology user might also choose to use the Tab key from the Element Path to Exit TinyMCE and move on to any content that might appear after the editor."

[16:06:33 CST(-0600)] <colinclark> oh

[16:06:35 CST(-0600)] <cindyli> basically, alt F11 jump to element path, then tab

[16:06:43 CST(-0600)] <colinclark> interesting

[16:07:11 CST(-0600)] <colinclark> That wouldn't work for someone not using an assistive technology, would it?

[16:07:34 CST(-0600)] <cindyli> right

[16:09:13 CST(-0600)] <colinclark> Any other creative ideas for how we might be able to work around it?

[16:09:27 CST(-0600)] <colinclark> Sounds like Tiny is just built not to work with anything but a mouse or a screen reader

[16:47:26 CST(-0600)] <cindyli> michelled: i've created a jira for the customization of CKEditor toolbar - http://issues.fluidproject.org/browse/STUDIO-26. Feel free to modify if anything I missed

[16:47:40 CST(-0600)] <michelled> thanks cindyli

[16:47:44 CST(-0600)] <cindyli> np

[16:52:23 CST(-0600)] <cindyli> michelled, colinclark, i submitted a pull request for the bullets display fix - https://github.com/fluid-project/studios.fluidproject.org/pull/24

[16:52:28 CST(-0600)] <colinclark> yay!

[16:52:32 CST(-0600)] <cindyli> finally, i can go home

[16:52:33 CST(-0600)] <colinclark> go home!

[16:52:38 CST(-0600)] <cindyli> )

[16:52:40 CST(-0600)] <colinclark> thank you so much for staying late

[16:52:45 CST(-0600)] <colinclark> As always, you rule

[16:52:48 CST(-0600)] <cindyli> no problem

[16:52:51 CST(-0600)] <cindyli> haha