[JBoss JIRA] (JBIDE-18030) Update BrowserSim/CordovaSim Skins
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18030?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-18030:
-------------------------------------------
Fix Version/s: 4.4.x
(was: 4.3.x)
> Update BrowserSim/CordovaSim Skins
> ----------------------------------
>
> Key: JBIDE-18030
> URL: https://issues.jboss.org/browse/JBIDE-18030
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Reporter: Burr Sutter
> Assignee: Konstantin Marmalyukov
> Fix For: 4.4.x
>
> Attachments: default_Devices.png, Screenshot 2014-03-13 08.37.41.png
>
>
> Due to the fast pace world of mobile computing, some of our skins have become a wee bit outdated (see attached image).
> - RIM Blackberry Bold Touch 9000
> - Apple iPhone 3
> + Samsung Galaxy S4
> And what is the vendor for "Galaxy Note II" and "Galaxy S III"?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-17442) BrowserSim crash on Fedora 20 when browsing jQuery Mobile app
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17442?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-17442:
-------------------------------------------
Fix Version/s: 4.4.x
(was: 4.3.x)
> BrowserSim crash on Fedora 20 when browsing jQuery Mobile app
> -------------------------------------------------------------
>
> Key: JBIDE-17442
> URL: https://issues.jboss.org/browse/JBIDE-17442
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.0.Beta1
> Environment: Fedora 20
> JBoss Developer Studio 8.0.0.Beta1
> webkitgtk-2.2.7-1.fc20.x86_64
> Reporter: Vineet Reynolds
> Assignee: Konstantin Marmalyukov
> Fix For: 4.4.x
>
>
> BrowserSim crashes when launching the TicketMonster app (from WFK 2.6). The offending line of code seems to be :
> {noformat}
> $("#container").enhanceWithin();
> {noformat}
> in the mobile {{router.js}}. The [enhanceWithin API|http://api.jquerymobile.com/enhanceWithin/] is new in jQueryMobile 1.4.x. The same line works without any flaw in BrowserSim on Windows and Mac OS X. It also works without problems in Chrome 34 and Firefox 28 on Fedora 20.
> The crash occurred on both GTK2 and GTK3 engines.
> Additional notes - strace output reveals that BrowserSim is terminated due to a SIGTRAP event, which is a bit weird.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-16141) Part of text obscured in Firebug Lite window
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16141?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-16141:
-------------------------------------------
Fix Version/s: LATER
(was: 4.3.x)
> Part of text obscured in Firebug Lite window
> --------------------------------------------
>
> Key: JBIDE-16141
> URL: https://issues.jboss.org/browse/JBIDE-16141
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.1.CR1
> Environment: Fedora 19 gnome
> Build id: CR1-v20131124-0717-B560
> Reporter: Michelle Murray
> Assignee: Konstantin Marmalyukov
> Fix For: LATER
>
> Attachments: BrowserSim_Fb_hiddentext.png
>
>
> Open an application in BrowserSim. Right-click simulated device and click debug>firebug lite. When firebug lite window opens, part of the test is obscured behind 'html'.
> !BrowserSim_Fb_hiddentext.png!
> Clicking through 'console', 'html', 'css' etc. buttons causes the text to become obscured and unobscured repeatedly. In one instance multiple clicking seemed to resolve the problem.
> This is perhaps an upstream issue but reporting here as a first port of call.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-13364) Consider changing the way in which BrowserSim uses WebKit engine
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13364?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-13364:
-------------------------------------------
Fix Version/s: 4.4.x
(was: 4.3.x)
> Consider changing the way in which BrowserSim uses WebKit engine
> ----------------------------------------------------------------
>
> Key: JBIDE-13364
> URL: https://issues.jboss.org/browse/JBIDE-13364
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Reporter: Yahor Radtsevich
> Assignee: Konstantin Marmalyukov
> Fix For: 4.4.x
>
>
> A perfect solution for BrowserSim must match the following criteria:
> * Be Java-based
> * Allow to fully customize the application window [skinning]
> * Work on every supported platform (Windows, Mac and Linux)
> * Use browser already installed in the system [to avoid library conflicts and reduce the size of our plugins]
> * Allow to execute JavaScript and/or modify DOM [to simulate some mobile * JavaScript events and Cordova API]
> * Allow to change User-Agent header
> * Allow to disable web security or support extensions [for Cordova cross-domain requests]
> * Support debugging protocol or support extensions [for better LiveEdit/LiveReload]
> * Support debugging protocol or ability to launch Web Inspector/Chrome Developer Tools [for JavaScript debugging capabilities]
> Unfortunately, there is no perfect solution, at least I do not know any.
> This is the list of the libraries I consider for BrowserSim (+=Pros, -=Cons, ?=questionable):
> * Java wrapper for [Chromium Embedded Framework|http://code.google.com/p/javachromiumembedded/]
> ** + I was able to run it on Windows
> ** - It failed in a half of a minute :)
> ** - Not supported since 2010
> ** ? probably will work better with the most recent version of CEF
> ** ? looks like there is no Linux support
> * [Qt WebKit bindings for SWT|http://code.google.com/p/qtwidgetsinswt/]
> ** + I was able successfully run on Windows (32-bit) with Qt 4.8 and MinGW
> ** + At least during my smoketesting it did not fail
> ** - The plugin page claims that only win32 and cocoa32 are supported
> ** - requires Qt (and MSVC or MinGW for Windows) libraries to be bundled with it
> ** - Does not have existing API for invoking JavaScript.
> ** - Not supported since 2010
> ** ? I do not know how easy it would be to run it on Linux
> ** ? I do not know if it will work with Qt 5
> * [AppJS|http://appjs.org/] - a JavaScript SDK for creating Chromium based desktop applications
> ** + Supports Windows, Mac and Linux!
> ** + Allows to disable web security
> ** + Has active community
> ** + Did not fail at my smoketest
> ** ? need to ensure that applications may be run without borders
> * [node-webkit|https://github.com/rogerwang/node-webkit#readme] - the idea is the same as with AppJS - allows to create desktop apps with JavaScript
> ** + supported by Intel in some way
> ** ? I did not try it yet
> * [Google Chrome Frame|http://www.google.com/chromeframe]
> ** + the only way to embed _already installed_ Chrome into our application (all other require libraries to be bundled)
> ** - Windows only
> ** - [no success to use it as Ole object|http://code.google.com/p/chromium/issues/attachmentText?id=25448&a...]
> ** ? Probably will work if use it with Browser(SWT.NONE)
> * Stay with existing SWT bindings for WebKit
> ** + We already use it
> ** + Support all platforms
> ** + Allow JavaScript to be executed
> ** + Do not require to be bundled with our plugins
> ** + Allow skinning
> ** - Require Safari on Windows [no updates since May 9, 2012]
> ** - Web security cannot be disabled
> ** - Do not support extensions
> ** - Do not support remote debugging protocol
> ** - Do not support Web Inspector/Chrome Developer Tools
> *To conclude:*
> * Firstly, moving to a JavaScript SDK potentially could resolve all our problems, but now I do not think it is worth it.
> * Secondly, it would be great if we had good SWT bindings for Chromium, but they do not exist. The only way to get them is to implement them by ourself.
> * Thirdly, the last option does not look too bad. And probably it does not worth it to create Chromium bindings or to move to another non-Java language. Especially, if we would be able to create a good workaround for cross-domain requests for Cordova, then almost everything else is ok.
> * Fourthly, the biggest issue with existing SWT bindings is that Safari is not supported anymore on Windows. It is an OS specific issue and we could consider a replacement of SWT bindings on Windows only (e.g. use Chrome Frame or Qt on Windows).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months