@tisola Can you open a corresponding tracker item in the feature tracker (http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8549) and link back here?

Also have a look at how this is done in the html5 chrome and use the same approach. This will also fix the issue @beat mentioned with the missing class = "...".

And if you're at it, wouldn't it make sense to add those parameters to other chromes there as well (where appropriate)?

Why is it failing the test? Like @mbabker stated, is Travis failure unrelated in this case?

@tisola Looks unrelated to this change as I have the same error in a completely different PR. It's somehow related to some registry stuff where <node name="booleanfalse" type="boolean"></node> is expected but <node name="booleanfalse" type="boolean"/> returned.

It's something in JRegistry which is behaving differently depending on the
environment configuration. Unrelated to this.

On Friday, November 22, 2013, Thomas Hunziker wrote:

@tisola https://github.com/tisola Looks unrelated to this change as I
have the same error in a completely different PR. It's somehow related to
some registry stuff where is expected but name="booleanfalse" type="boolean"/> returned.

—
Reply to this email directly or view it on GitHub#2572 (comment)
.

Hi @tisola

is this issue still valid? As the last comment here was on 22 Nov 2013? Also pull requests to the master branch of this repo are not longer accepted. Can you close this pull request and submit a new one against the staging branch, if this issue still exists?
If there is no Response in a month we will close the PR here.

Thanks for understanding!

Set to "closed" on behalf of @vdespa by The JTracker Application at issues.joomla.org/joomla-cms/2572