Closed (fixed)
Project:
D7 Media
Version:
7.x-2.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Jul 2011 at 13:37 UTC
Updated:
12 Oct 2011 at 16:11 UTC
Jump to comment: Most recent file
Comments
Comment #1
wwedding commentedPatch tested here and it did the trick, no more terrible popup behavior.
Comment #2
idflood commentedI confirm the patch is working great and the code looks good. It was not applying anymore, so here is a simple reroll.
Comment #3
dboulet commentedPatch works for me too, thanks. Maybe we should add a small comment in the code to explain the changes here?
Comment #4
idflood commentedHere is the same patch as above with added comment. I've chosen to use a shortened version of the current issue title: fix broken popup browser when using "add another item"
Comment #5
LSU_JBob commentedHere's a patch so you're not hardcoding zero into the index, and putting a check to make sure the array is not empty just so the code can be bullet proof.
Comment #6
slashrsm commentedFixed just one whitespace issue, therefore I upload a new patch. Besides from that everything stays the same. I think we agree, that this could be commited.
Comment #7
dboulet commentedFixed a few more spacing issues.
Comment #8
LSU_JBob commentednice, thanks guys
Comment #9
dboulet commentedFound one more space issue and simplified the code a little.
Comment #10
LSU_JBob commentedI still kinda like the if statements broken out, means it doesn't have to evaluate two, just one before anything else goes on. I think at this point though stuff like this is trvial
I think we should go with patch in #7
Comment #11
dboulet commentedLSU_JBob, the patch in #9 does the exact same thing. If the first condition for the if evaluates to false, that value will be returned and the second condition will be ignored. I see no reason to split it into two ifs.
Comment #12
idflood commentedThe patch in #9 looks good. Just one suggestion maybe, why not use the jQuery.isArray() function? I think it makes the code more clear.
Here is a patch identical as #9, except that it uses the $.isArray function.
ref: http://api.jquery.com/jQuery.isArray/
Comment #13
idflood commentedOne minute after I posted the last patch I thought about one more simplification. Since we assign options.widget.src to browserSrc we can use that variable for the condition and value assignment too.
Comment #14
dboulet commentedNice. Now we just need the maintainers to take a look at it.
Comment #15
acbramley commentedWorks for me. Let's get this committed!
Comment #16
minneapolisdan commentedThanks for the patch, I used #13 and it seems to have fixed the issue.
Comment #17
rickvug commentedThe patch in #13 is dead simple. Let's get it in as this bug will effect a lot of users.
Comment #18
rickvug commentedI tested the patch in #13 and it does not work for me. I'm using the Rubik theme, not sure if that would make a difference. I went back to the very first patch posted and had success with that.
Comment #19
idflood commented@rickvug: what browser are you using?
Comment #20
rickvug commented@idflood Chrome 13 for Mac.
Comment #21
idflood commentedI've tried to reproduce the issue described in #18 without luck. Tested on chrome 13 on osx, with first and last patch and they are both working. Tried again after insalling tao and rubick with rubick as the admin theme, and both patches are still working.
The important thing is that one of these patch get commited. Then it will be easier to fix edge cases.
@rickvug: Any idea of other modules / changes you made that may affect the result?
Comment #22
bforchhammer commentedSubscribe
Comment #23
ParisLiakos commentedSubscribing!will test the patch later
Comment #24
rickvug commented@rootatwc @idflood Sorry that I haven't been able to get back to testing again. If you can't reproduce the problem feel free to commit the patch. If the problem crops up for me again I'll comment further.
Comment #25
ParisLiakos commentedTested and works with both chrome and firefox in Linux!
As per #24,Please commit this!
Comment #26
ParisLiakos commentedAlso tested it against 7.x-1.x.works there too!!
Can someone commit it on both branches?its an anoying bug:p
Comment #27
idflood commentedThe issue still exists in 7.x-2.x. The patch in #13 still apply and fix it. please commit
Comment #28
dave reidCommitted #13 to both branches. Thanks!
http://drupalcode.org/project/media.git/commit/1748396
http://drupalcode.org/project/media.git/commit/1d9bdfe