Adobe CEP extension panel debugger via localhost:[port]
Reported by
adverton...@gmail.com,
Oct 25 2016
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 Steps to reproduce the problem: 1. Open Developer Tools to debug Adobe CEP panel via localhost:[port] 2. Enter command in the console + hit enter 3. A new line is inserted instead of submitting the command What is the expected behavior? Execute the command. What went wrong? When debugging an Adobe CEP extension panel via localhost:[port] if you press enter in Chrome Version 54.0.2840.71 m (64-bit) it does not submit the command. Instead of submitting the command an unexpected new line is inserted. Did this work before? N/A Chrome version: Version 54.0.2840.71 m (64-bit) Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Oct 25 2016
,
Oct 26 2016
advertonic.kft@, In order to triage this issue could you please provide the following details (1)Sample extension or url of adobe cep panel (2)sample command and expected output Thank You...
,
Oct 26 2016
I have downloaded and modified a sample extension from https://github.com/Adobe-CEP/Samples It has to be in Photoshop's: C:\Users\<userName>\AppData\Roaming\Adobe\CEP\extensions folder on windows. I have made a .debug file in it to be able to debug it on port localhost:8011 Added a windows registry key to be able to test it: HKEY_CURRENT_USER/Software/Adobe/CSXS.6 >>> add a key named PlayerDebugMode, of type String, and value 1. If Photoshop is running and the extension "CEP HTML Panel 1" is open; when I try to debug it with Chrome by opening localhost:8011, the command line is't working.
,
Oct 27 2016
,
Oct 28 2016
This is due to KeyboardEvent.keyIdentifier removal from the spec. The workarounds are: - pass --remote-debugging-targets=localhost:port to chrome on startup, then connect from the chrome://inspect page; - use older Chrome version. Sorry for inconvenience.
,
Oct 28 2016
:( another glitch to patch. Thanks for the answer but I am disappointed with this. The debugging process now: 1. Open browser. 2. Connect to localhost:port of the CEP engine. 3. Open another tab. 4. Navigate to chrome://inspect 5. Find the CEP Extension tab amongst the other open tabs and select it This isn't seems like fast or comfortable. I have to rethink my debugging intent now. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by adverton...@gmail.com
, Oct 25 2016