Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
After upgrading to 2.2.0, <input> tag 'readonly' attribute is not rendered #151
Hi there, after I upgraded email@example.com to firstname.lastname@example.org in our Meteor app, the 'readonly' attributes on tag are no longer rendered. This only happens if the tag has some dynamically generated attributes, for example:
This one works correctly:
I replicated the problem also in "Todos" example app. I cloned the repo from https://github.com/meteor/todos, updated meteor and all packages to their latest versions and have the same problem (actually I tested the above code in Todos app). When I downgraded to email@example.com, readonly attribute is rendered (although not as boolean attribute like 'disabled', but that's another story). Strangely enough, other attributes like 'disabled' are rendered normally.
I done some tests with my project.
Any helper like
I also test an input like jancurn said:
For me works fine.
With the same example, the debug shows me:
The first object is the attributes declared in HTML. But
But HTML.isNully don't interpret the value false as nully, adding it to the list that render attributes. So HTML is still rendered in the wrong way with
People are reporting success with changing the attribute name from
So if perhaps this is a case sensitivity issue, can't we just make the name comparison in