Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 371013 - make debug work on tabs within a Chrome instance
Summary: make debug work on tabs within a Chrome instance
Status: RESOLVED FIXED
Alias: None
Product: Orion
Classification: ECD
Component: Client (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: 0.4 RC1   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-08 16:41 EST by Grant Gayed CLA
Modified: 2012-02-09 10:49 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Grant Gayed CLA 2012-02-08 16:41:04 EST 

    


    


      



        
          Comment 1
        

        
          Grant Gayed CLA

        

        
        

        
          2012-02-08 17:16:28 EST
        

      






I've pushed the changes to the following repo, to be picked up:

- repo: git://github.com/ggayed/orion.client.git
- branch: Bug371013
- commit: https://github.com/ggayed/orion.client/commit/f414cc8014a6acc51e666c3487a0e6594aec6835

Changes:
- now works for tabs within the same Chrome instance as Orion is running in (includes windows detached from the Chrome instance), so no port # is required
- remote debugging has been disabled (though this code is still there awaiting further investigation)
- the Connections and Debug pages now display instructional labels if a non-Chrome or Chrome-without-the-extension case is detected
- if the Chrome extension is missing (or is old) then provides a link for installing it
- fixed bug with url display not updating when navigating a tab between pages within a domain