Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

number of words instead of number of list items announced when <li> set to inline or inline-block used #2151

Closed
nvaccessAuto opened this Issue Mar 6, 2012 · 11 comments

Comments

Projects
None yet
2 participants

Reported by zomigi on 2012-03-06 21:53

Steps to reproduce:

  1. Create a list (
      element) in an HTML page
    • Set the CSS of the
    • elements to display:inline or display:inline-block
    • Have NVDA read the list in the web page

Expected results:

NVDA announces number of list items (

  • elements) when entering the list.

    Actual results:

    NVDA announces number of words within all the list items when entering the list. For instance, if the list contains 4 items and each have 2 words in them, NVDA will say the list contains 8 items, not 4.
    Blocked by #3546
    Blocking #3672

  • Attachment NVDA-bug.html added by zomigi on 2012-03-06 21:55
    Description:
    contains same list 3 times, each with different CSS display value, announced 2 different ways

    Comment 1 by jteh on 2012-03-07 02:54
    What browser(s) did you test this with?

    Comment 2 by zomigi on 2012-03-07 22:02
    The bug occurs in Firefox 10.0.2. It doesn't occur in IE 8. Those are the only two browsers I checked.

    Comment 3 by jteh on 2012-06-14 22:33
    This occurs because we use the child count of the list, but for inline and inline-block, this includes the whitespace nodes between the list items.

    See also MozillaBug:764757 regarding inline-block.
    Changes:
    Milestone changed from None to near-term

    Comment 4 by jteh on 2012-06-15 09:51
    Mick, should we try to spoof the _childcount attribute (which is currently generated by storage) or should we come up with a new attribute like itemcount or similar and have speech use that as first preference?

    Comment 5 by mdcurran on 2013-09-16 06:45
    Changes:
    Milestone changed from near-term to next

    Comment 6 by Michael Curran <mick@... on 2013-09-16 06:50
    In [051bc82]:

    Merge branch 't2151' into next. Incubates #2151
    
    

    Changes:
    Added labels: incubating

    Comment 7 by leonarddr on 2013-09-16 08:07
    I could only redistribute this problem in firefox, not in Chrome or IE. May be the what's new entry should mention a Mozilla specific fix?

    Comment 8 by mdcurran on 2013-09-16 21:48
    True that the case was probably mostly seen in Firefox, but the code path certainly allowed for it in either.

    Comment 10 by Michael Curran <mick@... on 2013-10-15 09:39
    In [8f8563c]:

    Merge branch 't2151'. Fixes #2151
    
    

    Changes:
    Removed labels: incubating
    State: closed

    Comment 11 by mdcurran on 2013-10-15 09:39
    Changes:
    Milestone changed from next to 2013.3

    @nvaccessAuto nvaccessAuto added this to the 2013.3 milestone Nov 10, 2015

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment