[JBoss JIRA] (JBIDE-14075) Firebug lite closes when I follow or open a new url
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14075?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov resolved JBIDE-14075.
--------------------------------------------
Resolution: Won't Fix
> Firebug lite closes when I follow or open a new url
> ---------------------------------------------------
>
> Key: JBIDE-14075
> URL: https://issues.jboss.org/browse/JBIDE-14075
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Reporter: Max Rydahl Andersen
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Attachments: screenshot-1.png
>
>
> EXECUTE: Open Browersim on a site (i.e. http://dr.dk)
> EXECUTE: Right click > Fire Bug Lite
> ASSERT: fire bug shows up showing content for the current page
> EXECUTE: Click link or type in new url on browsersim that is different from previous site
> ASSERT: fire bug updates to show content for the current page
> the last ASSERT fails - firebug lite window closes down forcing users to again right click on skin click firebug lite.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-14075) Firebug lite closes when I follow or open a new url
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14075?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-14075:
-------------------------------------------
Fix Version/s: 4.3.x
> Firebug lite closes when I follow or open a new url
> ---------------------------------------------------
>
> Key: JBIDE-14075
> URL: https://issues.jboss.org/browse/JBIDE-14075
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Reporter: Max Rydahl Andersen
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Fix For: 4.3.x
>
> Attachments: screenshot-1.png
>
>
> EXECUTE: Open Browersim on a site (i.e. http://dr.dk)
> EXECUTE: Right click > Fire Bug Lite
> ASSERT: fire bug shows up showing content for the current page
> EXECUTE: Click link or type in new url on browsersim that is different from previous site
> ASSERT: fire bug updates to show content for the current page
> the last ASSERT fails - firebug lite window closes down forcing users to again right click on skin click firebug lite.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-8874) Support XML documents for XSLT compliant browser
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8874?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov updated JBIDE-8874:
------------------------------------------
Fix Version/s: LATER
(was: 4.3.x)
> Support XML documents for XSLT compliant browser
> ------------------------------------------------
>
> Key: JBIDE-8874
> URL: https://issues.jboss.org/browse/JBIDE-8874
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 3.3.0.M1
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Fix For: LATER
>
> Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png, screenshot59.png, wecandoit.png, xml-xsl.png
>
>
> Would be good to have support to show documents for XSLT compliant browser like
> {code:title=cdcatalog.xsl|borderStyle=solid}
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <!-- Edited by XMLSpy® -->
> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
> <xsl:template match="/">
> <html>
> <body>
> <h2>My CD Collection</h2>
> <table border="1">
> <tr bgcolor="#9acd32">
> <th>Title</th>
> <th>Artist</th>
> </tr>
> <xsl:for-each select="catalog/cd">
> <tr>
> <td><xsl:value-of select="title"/></td>
> <td><xsl:value-of select="artist"/></td>
> </tr>
> </xsl:for-each>
> </table>
> </body>
> </html>
> </xsl:template>
> </xsl:stylesheet>
> {code}
> {code:title=page.xml|borderStyle=solid}
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <?xml-stylesheet type="text/xsl" href="cdcatalog.xsl"?>
> <!-- Edited by XMLSpy® -->
> <catalog>
> <cd>
> <title>Empire Burlesque</title>
> <artist>Bob Dylan</artist>
> <country>USA</country>
> <company>Columbia</company>
> <price>10.90</price>
> <year>1985</year>
> </cd>
> <cd>
> <title>Hide your heart</title>
> <artist>Bonnie Tyler</artist>
> <country>UK</country>
> <company>CBS Records</company>
> <price>9.90</price>
> <year>1988</year>
> </cd>
> <cd>
> <title>Greatest Hits</title>
> <artist>Dolly Parton</artist>
> <country>USA</country>
> <company>RCA</company>
> <price>9.90</price>
> <year>1982</year>
> </cd>
> </catalog>
> {code}
> Visual part of editor would look like:
> !screenshot59.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-9292) Show as EL toolbar button does not affect values set through Page Design Options dialog
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-9292?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov updated JBIDE-9292:
------------------------------------------
Fix Version/s: LATER
(was: 4.3.x)
> Show as EL toolbar button does not affect values set through Page Design Options dialog
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-9292
> URL: https://issues.jboss.org/browse/JBIDE-9292
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 3.3.0.M1
> Reporter: Maxim Areshkau
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Fix For: LATER
>
> Attachments: el-pressed.png, page-design-options.png, show-el-not-pressed.png
>
>
> *Steps to reproduce:*
> # Create a JSF project
> # Create a JSPX page with the following content:
> {code:xml|title=test.jspx}
> <input type="submit" value="${hello}"/>${hello}
> {code}
> # Open Page Design Options dialog->Substitutes EL-expressions
> # Create expression {{hello}} with value {{Hello World!}} and press OK
> # Click show bundle's messages as EL expressions button on the toolbar
> *Actual result:*
> ${hello} expressions are substituted by {{Hello World!}}
> *Expected result:*
> ${hello} expressions are not substituted and shown as is
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-4644) Undo (Ctrl+Z) works wrong with taglib's declaration after insertating from context menu
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-4644?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov updated JBIDE-4644:
------------------------------------------
Fix Version/s: LATER
(was: 4.3.x)
> Undo (Ctrl+Z) works wrong with taglib's declaration after insertating from context menu
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-4644
> URL: https://issues.jboss.org/browse/JBIDE-4644
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 3.1.0.M3
> Environment: The priority has been changed to MINOR
> Reporter: Yura Zhishko
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Fix For: LATER
>
> Attachments: screenshot-1.jpg
>
>
> 1) Open blank page (reproducible only for blank pages)
> 2) Choose "Insert tag from Palette" -> Around/After/Before/Into -> and insert any tag
> ASSERT: Tag appears with taglib definition
> 3) Press Ctrl+Z
> ASSERT: Tag and taglib definition disappear (screenshot-1)
> ASSERT FAILED: Only tag disappear (screenshot-2)
> P. S. This issue apply to source and visual context menus.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-4791) Properties list in Properties view disappears when the user clicks a tab in CSS Properties view
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-4791?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov updated JBIDE-4791:
------------------------------------------
Fix Version/s: LATER
(was: 4.3.x)
> Properties list in Properties view disappears when the user clicks a tab in CSS Properties view
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-4791
> URL: https://issues.jboss.org/browse/JBIDE-4791
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 3.1.0.M3
> Environment: Ubuntu 8.10, JBossTools revision 17062
> Reporter: Olga Chukhutsina
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Fix For: LATER
>
> Attachments: CSSPropertiesBug_1.png, CSSPropertiesBug_2.png
>
>
> Properties list disappears from Properties view when the user clicks tabs in CSS Properties view.
> Steps:
> Choose some selector in CSS file>Text/Font tab is opened in CSS Properties view by default and the properties list in Properties view is displayed>choose another tab in CSS Properties view(e.g Background )>now properties list in Properties view is not shown any more
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-20674) Write automated tests to check consistency of Jetty between JBT & Eclipse
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20674?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov resolved JBIDE-20674.
--------------------------------------------
Resolution: Out of Date
Resolving as out of date since jetty have fix semantic version problems, so Eclipse help can stay with any version of Jetty
> Write automated tests to check consistency of Jetty between JBT & Eclipse
> -------------------------------------------------------------------------
>
> Key: JBIDE-20674
> URL: https://issues.jboss.org/browse/JBIDE-20674
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim, livereload, target-platform
> Reporter: Mickael Istria
> Assignee: Konstantin Marmalyukov
> Fix For: 4.4.0.Alpha1
>
>
> Since it appears Jetty is somehow a "weak" component (ie APIs are often broken and versions are not well managed), we often have to enforce a specific version of Jetty for our JBoss Tools bundles. However, it happens that the version used by JBoss Tools component isn't the same as the one shipped by some other Eclipse components.
> We need to make sure that enforcing a version of Jetty doesn't break those Eclipse components. The best way to achieve that is to write a test trying to validate the correct work of any Eclipse component we're aware it's using Jetty, as part of the same test plugin that validates the JBoss Tools components.
> The list of identified Eclipse component using Jetty so far:
> * Equinox (but I don't know how it uses Jetty, so neither how to make sure it's working well)
> * Eclipse Help (test coulod load the help and make sure it shows content and not a 302 or 500 HTTP error)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months