User tests: Successful: Unsuccessful:
In our Joomla install the iFrame wrapper objects were not auto-sizing in Firefox. This change fixes that issue.
Thanks for your contribution - At this time we are only using github as the place to submit code fixes, the actual reporting of issues and testing fixes is still taking place on Joomlacode.
As it has been some time since you opened this issue can you please confirm that it is still valid with the current Master or Joomla 3.2 beta. If it is no longer valid then please can you close this issue. Otherwise please can you:
1) Open an item on the Joomlacode tracker in the appropriate area.
CMS Bug Reports: http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103
CMS Feature Requests: http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8549
2) After submitting the item to the Joomlacode tracker, add a link to the Joomlacode tracker item here and make sure that you add a link to this GitHub issue or pull request on the joomlacode tracker item.
The Joomlacode tracker was pretty hard to navigate, and there are thousands of bugs in there with no apparent way to filter to open ones. This makes contribution pretty difficult. I'm going to close this bug - it's up to you guys to either make it easier for people to contribute or fix the issue yourselves. I mean this in the most constructive way possible, but reducing the barrier to entry is part of the burden of running an open source project.
If you are logged in to joomlacode then you have a full suite of tools to
help sort and filter[image: Inline images 1]
On 17 October 2013 14:21, Jonathan Klein notifications@github.com wrote:
The Joomlacode tracker was pretty hard to navigate, and there are
thousands of bugs in there with no apparent way to filter to open ones.
This makes contribution pretty difficult. I'm going to close this bug -
it's up to you guys to either make it easier for people to contribute or
fix the issue yourselves. I mean this in the most constructive way
possible, but reducing the barrier to entry is part of the burden of
running an open source project.—
Reply to this email directly or view it on GitHub#1234 (comment)
.
Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/
Okay fair enough, but that still requires creating another account, and then sifting through the 500+ open bugs to make sure I'm not submitting a duplicate. I can filter by category, but some of the categories appear to overlap. For example, does this go into "Browsers", "JavaScript", or "Front End"?
Basically what I'm getting at is that the process feels tedious. Nicholas Zakas has written eloquently about this on Smashing Magazine (and even quoted me): http://coding.smashingmagazine.com/2013/01/03/starting-open-source-project/. I have limited time, and the motivation just isn't there to contribute to Joomla given how many hoops I have to jump through, and how long it takes to get feedback on issues. After all, it took 5 months for me to be updated on the status of this pull request, and told about the "appropriate" mechanism for submission.
Tested on IE7, IE8, IE9, Firefox latest and Chrome latest.