Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 339561

Summary:	[crossfire] connecting to an already suspended browser does not put client in the correct state
Product:	[WebTools] JSDT	Reporter:	Michael Rennie <Michael_Rennie>
Component:	Debug	Assignee:	Project Inbox <jsdt.debug-inbox>
Status:	RESOLVED WONTFIX	QA Contact:	Michael Rennie <Michael_Rennie>
Severity:	normal
Priority:	P3	CC:	grant_gayed, thatnitind
Version:	3.3
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Michael Rennie

2011-03-10 12:51:07 EST

code from HEAD

If you connect the crossfire client to a browser that is already suspended - at a breakpoint for example - the client will not be in the correct state.

Steps:
1. start FF3.x + crossfire
2. navigate to www.eclipse.org/swt/repeat.html
3. breakpoint on line 6, F5 to refresh and suspend
4. connect JSDT to FF

Expected:
the JSDT client would also be in the suspended state allowing me to immediately debug

Happens:
nothing, the client connects and is in the running state - with no way to force it into the suspended state. The only recourse if to resume FF and have it suspend again once the client is connected.

Comment 1 Michael Rennie

2013-11-12 13:58:45 EST

In a future release of Firebug, Crossfire support will be dropped completely in favour or JSD2 and RDP, as such no more bugs will be fixed for the Crossfire support.

See:
1. https://wiki.mozilla.org/Firebug/WeeklyUpdates/2013-11-05#Crossfire
2. https://getfirebug.com/wiki/index.php/JSD2_Adoption
3. https://wiki.mozilla.org/Debugger