Closed Bug 1422579 Opened 8 years ago Closed 8 years ago

Onclick on image in iframe is on 58beta done 2 times (accidently?)

Categories

(Firefox :: Untriaged, defect)

Product:
Firefox
Component:
Untriaged
Version:
58 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: zdnexnet, Unassigned)

Details

(Keywords: testcase-wanted)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20171128222554 Steps to reproduce: It looks like in current version from 56>58 it is sometimes possible to load page with iframe where are images. Main page adds on images onclick event. via image.onclick = function(){} call can be done 2 times but developer tools does not seem to show that click is done 2 times but server clearly shows that 2 requests were done via ajax (they are in log with different timing) I have managed to do this 6 times today and also like 4 times 2 weeks ago with reloading page. When I have used SHIFT and RELOADED page again completely it was suddenly okay and there was only one event done on JS and on server log. I have used another browsers/versions and I was not able to do it again. I am suspecting cache of iframe and weird onclick assigment which could lead to this. My question is this in current architecture possible if image has direct onclick assigment which should remove all previus events set to this? I do not have any test which confirms this, so this is question to developers if it is actually possible. Actual results: Two clicks are done even it looks like ff thinks only one is done. Expected results: One click should be done
Keywords: testcase-wanted
Ok, it seems I have found reason for this - it is not problem of 2 clicks/etc (I was wrong with initial assumption). It is synchronization between more windows and localStorage. It seems that if Storage Event is called in all windows somehow all this is done at all windows immediately, so other windows cannot just check value which is added to localStorage. So it looks like current version is doing it so fast. Chrome does not have this problem. Ok I think this bug is wrong and I will try to add testcase for this as it looks I have found what is going on. I am sorry, that first information about this were wrong:(
Closing this as invalid, maybe in future I will add testcase for localStorage in more windows.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.