Closed
Bug 816997
Opened 12 years ago
Closed 8 years ago
Asp.Net CustomCallBack Event don't work with Firefox 18 beta 2
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: dazzim72, Unassigned)
Details
(Keywords: regression, Whiteboard: [closeme 2016-04-17])
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.91 Safari/537.11 Steps to reproduce: In Asp.Net I have a button and I use the behind event CustomCallBack to manage the click Actual results: Nothing, it seems the event is not fired Expected results: It should fire the event and execute the Vb.NET code
Reporter | ||
Comment 1•12 years ago
|
||
I test with version 17 and it works well
Comment 2•12 years ago
|
||
Marco, if you could provide a public testcase and/or help us find the regressing change via http://mozilla.github.com/mozregression/, that would help resolve this problem quickly.
tracking-firefox18:
--- → ?
tracking-firefox19:
--- → ?
tracking-firefox20:
--- → ?
Keywords: regression
Comment 3•12 years ago
|
||
This bug isn't yet actionable by QA/engineering in any way, since there is no URL/testcase. Let's get this re-nominated when that changes.
Comment 4•8 years ago
|
||
Hi Marco, Can you please provide a test case or a URL so we can test this? Is this still reproducible on your end ? If yes, can you please retest this using latest FF release and latest Nightly build (https://nightly.mozilla.org/) and report back the results ? When doing this, please use a new clean Firefox profile, maybe even safe mode, to eliminate custom settings as a possible cause (https://goo.gl/PNe90E). Thanks, Cosmin.
Flags: needinfo?(dazzim72)
Whiteboard: [closeme 2016-04-17]
Comment 5•8 years ago
|
||
Marking this as Resolved: Incomplete due to the lack of response from the reporter. If anyone can still reproduce it on latest versions, feel free to reopen the issue and provide more information. Thanks, Cosmin.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(dazzim72)
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•