These are chat archives for angular/material

10th
Feb 2015
Cosmin Ronnin
@kosz
Feb 10 2015 19:32
we're having an issue here with md-sidenav, it does not show up when it's inside an angular partial included with ng-include, under Firefox. Safari and Chrome works, and the sidenav shows up on firefox if we dump it's html directly into index.html, but if we include is a partial, it doesn't show up, we can highlight it with dev tools but it never shows up. Does anybody know anything about this ?
Marcy Sutton
@marcysutton
Feb 10 2015 19:37
@kosz is it a flexbox issue? Does the sidenav get wrapped in an extra tag that could be interfering? I debugged a similar issue in IE10 yesterday.
@dmackerman I'm seeing them fine in Chrome 40 on mac fwiw
Ed Pelc
@epelc
Feb 10 2015 19:44
@marcysutton do you know if you can use a label for two elements and be aria friendly?
Cosmin Ronnin
@kosz
Feb 10 2015 19:46
@marcysutton thanks for that info. it looks indeed, like on firefox the Sidenav setup wants to be a direct child of the <body> or it causes issues
Cosmin Ronnin
@kosz
Feb 10 2015 20:53
@marcysutton thanks again. your information has helped us understand and fix the problem.
Marcy Sutton
@marcysutton
Feb 10 2015 21:50
Yay!
@epelc <label> only pairs natively with <input> and <textarea> I believe, but you could always use aria-labelledby https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-labelledby_attribute
You can probably label multiple elements with that, I imagine
You can easily check what's happening with ARIA attributes in chrome://accessibility
@kosz I think it has to be a direct descendant of a flex parent, not necessarily the body
Ed Pelc
@epelc
Feb 10 2015 21:54
@marcysutton I think I have to switch to a single <input>. I was reading the spec and it says <label> only works with one.
I didnt know about chrome://accessibility though thanks