[JBoss JIRA] (JBIDE-14122) Add VJET to Central
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14122?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-14122:
-----------------------------------------
Yes, it looks like a warning... I suppose that the reason of this message could be the fact that we already have Apache Batik CSS v.1.6 installed. But VJET requires Apache Batik CSS v.1.7.
Probably some JBT (or JBDS) plug-in has a restriction to use Apache Batik CSS of version not later than v.1.6, so, the installation is decided to leave it (not to remove).
At least when I've being tested the VJET installation from Central, the installed VJET was working (its perspective appeared, JS-editor could be started).
> Add VJET to Central
> -------------------
>
> Key: JBIDE-14122
> URL: https://issues.jboss.org/browse/JBIDE-14122
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central, target-platform
> Affects Versions: 4.1.0.Beta1
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Beta1
>
> Attachments: installing-vjet-from-jbt-mirrors.png, installing-vjet-from-jbt-mirrors2.png, installing-vjet-from-jbt-mirrors3-problem-with-junit4.png, installing-vjet-from-jbt-mirrors4-success.png, installing-vjet-from-jbt-mirrors5-problem-with-junit4-SOLVED.png, JBIDE14122-central-with-vjet.png
>
>
> We should provide an ability to install VJET v.0.10 through Central
> The latest stable VJET Update Site: [http://download.eclipse.org/vjet/updates-0.10] - v.0.10.0, Released
> The following dependencies (in addition to what we already have in TP) are to be satisfied in order to run VJet:
> {code:title=Orbit bundles for VJET}
> <unit id="org.apache.xml.serializer" version="2.7.1.v201005080400"/>
> <unit id="org.apache.xml.resolver" version="1.2.0.v201005080400"/>
> <unit id="org.apache.batik.css" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.css.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.dom" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.dom.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.util" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.util.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.xerces" version="2.9.0.v201101211617"/>
> <unit id="org.ccil.cowan.tagsoup" version="1.2.0.v201202211000"/>
> <unit id="org.w3c.css.sac" version="1.3.1.v200903091627"/>
> <unit id="org.w3c.css.sac.source" version="1.3.1.v200903091627"/>
> <unit id="org.w3c.dom.svg" version="1.1.0.v201011041433"/>
> <unit id="org.w3c.dom.svg.source" version="1.1.0.v201011041433"/>
> <unit id="javax.xml" version="1.3.4.v201005080400"/>
> <unit id="org.apache.commons.collections" version="3.2.0.v2013030210310"/>
> <unit id="org.apache.commons.io" version="2.0.1.v201105210651"/>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-12321) handle IApplication#getEmbeddedCartridges correctly with changes to protocol 1.2
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12321?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12321:
-------------------------------------
Summary: handle IApplication#getEmbeddedCartridges correctly with changes to protocol 1.2 (was: handle IApplication#getEmbeddedCartridges correctly with changes to protocol 1.1)
> handle IApplication#getEmbeddedCartridges correctly with changes to protocol 1.2
> --------------------------------------------------------------------------------
>
> Key: JBIDE-12321
> URL: https://issues.jboss.org/browse/JBIDE-12321
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.0.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Beta1
>
> Attachments: app-type-listed-as-embedded.png
>
>
> In 1.1 the cartridges that you get reported when listing them on a application changed (IApplication#getEmbeddedCartridges):
> * 1.0:
> would report the embedded cartridges only
> * 1.1:
> would report the embedded cartridges and the application type (cartridge)
> !app-type-listed-as-embedded.png!
> see here: https://github.com/openshift/crankcase/pull/224
> The error that this caused was discussed here:
> https://bugzilla.redhat.com/show_bug.cgi?id=838611
> OpenShift pushed the discussed change (application-type reported as embedded cartridge) to protocol v1.1 and fixed the issue on the server-side. Our client, that currently requests protocol v1.0 has no issue since the fix. We have to make sure we support protocol 1.1 and are able to handle this correctly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-12320) support protocol version 1.2 in openshift-java-client
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12320?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12320:
-------------------------------------
Fix Version/s: 4.1.0.Beta1
(was: 4.1.x)
> support protocol version 1.2 in openshift-java-client
> -----------------------------------------------------
>
> Key: JBIDE-12320
> URL: https://issues.jboss.org/browse/JBIDE-12320
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.0.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Beta1
>
>
> The protocol for the OpenShift REST service has evolved over time and currently has v1.3. The rest service currently delivers 1.0, 1.1, 1.2 and 1.3.
> OpenShift Enterprise talks 1.2 and we therefore want to drop everything below it
> 2012-03-14 in #libra
> {quote}
> 07:08:20 PM) clayton: then adietish that's your answer - you're good to drop 1.1 and 1.0 support because we have no supported products in the field that use those api versions
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-13278) Rename "Run as->Run on server" at a JAX-RS Endpoint node level
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13278?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-13278:
-------------------------------------------
Yes Max, you have the behavior documented there. I think because it's consistent with the rest of the UI, it's good the way it is.
As such, I'm not sure we really want to change the menu to have a root "Test..." menu?
> Rename "Run as->Run on server" at a JAX-RS Endpoint node level
> --------------------------------------------------------------
>
> Key: JBIDE-13278
> URL: https://issues.jboss.org/browse/JBIDE-13278
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Webservices
> Affects Versions: 4.0.0.Final
> Reporter: Xavier Coulon
> Assignee: Brian Fitzpatrick
> Fix For: 4.1.0.Beta1
>
>
> The "Run as->Run on server" menu item work well, but they are no so obvious to the end-user. We should provide a more straightforward way to "test" the endpoint with the the WS Tester.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-14122) Add VJET to Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14122?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-14122:
------------------------------------
[~dgolovin] After that message, was installation able to proceed? Sounds like more of a warning than an error.
> Add VJET to Central
> -------------------
>
> Key: JBIDE-14122
> URL: https://issues.jboss.org/browse/JBIDE-14122
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central, target-platform
> Affects Versions: 4.1.0.Beta1
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Beta1
>
> Attachments: installing-vjet-from-jbt-mirrors.png, installing-vjet-from-jbt-mirrors2.png, installing-vjet-from-jbt-mirrors3-problem-with-junit4.png, installing-vjet-from-jbt-mirrors4-success.png, installing-vjet-from-jbt-mirrors5-problem-with-junit4-SOLVED.png, JBIDE14122-central-with-vjet.png
>
>
> We should provide an ability to install VJET v.0.10 through Central
> The latest stable VJET Update Site: [http://download.eclipse.org/vjet/updates-0.10] - v.0.10.0, Released
> The following dependencies (in addition to what we already have in TP) are to be satisfied in order to run VJet:
> {code:title=Orbit bundles for VJET}
> <unit id="org.apache.xml.serializer" version="2.7.1.v201005080400"/>
> <unit id="org.apache.xml.resolver" version="1.2.0.v201005080400"/>
> <unit id="org.apache.batik.css" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.css.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.dom" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.dom.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.util" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.util.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.xerces" version="2.9.0.v201101211617"/>
> <unit id="org.ccil.cowan.tagsoup" version="1.2.0.v201202211000"/>
> <unit id="org.w3c.css.sac" version="1.3.1.v200903091627"/>
> <unit id="org.w3c.css.sac.source" version="1.3.1.v200903091627"/>
> <unit id="org.w3c.dom.svg" version="1.1.0.v201011041433"/>
> <unit id="org.w3c.dom.svg.source" version="1.1.0.v201011041433"/>
> <unit id="javax.xml" version="1.3.4.v201005080400"/>
> <unit id="org.apache.commons.collections" version="3.2.0.v2013030210310"/>
> <unit id="org.apache.commons.io" version="2.0.1.v201105210651"/>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-14348) BrowserSim address string disappearing
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14348?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-14348:
----------------------------------------
If you hide the bar instantly when scrolling down, why don't show it instantly when scrolling up?
> BrowserSim address string disappearing
> --------------------------------------
>
> Key: JBIDE-14348
> URL: https://issues.jboss.org/browse/JBIDE-14348
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.0.Alpha2
> Reporter: Daniel Azarov
> Assignee: Yahor Radtsevich
> Fix For: 4.1.0.Beta1
>
>
> Test case:
> EXECUTE:
> 1. Create project
> 2. Create html file:
> {code}
> <html>
> <head>
> </head>
> <body>
> <a id="page1">1 Jump to this place</a>
> <p>
> aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg
> </p>
> <a id="page2">2 Jump to this place</a>
> <p>
> aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg
> </p>
> <a id="page3">3 Jump to this place</a>
> <p>
> aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg
> </p>
> <a id="page4">4 Jump to this place</a>
> <p>
> aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg
> </p>
> <a id="page5">5 Jump to this place</a>
> <p>
> aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg
> </p>
> <a id="page6">6 Jump to this place</a>
> <p>
> aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg
> </p>
> </body>
> </html>
> {code}
> 3. Open file with BrowserSim
> 4. Try to add #page3 to the address string
> FAIL:
> Address string disapeared
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-14358) Not able to generate JBOSS WS client code in eclispe Juno
by Roopa Chakra (JIRA)
Roopa Chakra created JBIDE-14358:
------------------------------------
Summary: Not able to generate JBOSS WS client code in eclispe Juno
Key: JBIDE-14358
URL: https://issues.jboss.org/browse/JBIDE-14358
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Environment: EAP 5.1.0
Reporter: Roopa Chakra
Tried installing JBoss tools (JBoss Tools (Juno) 4.0.1.Final from eclipse market place) to eclipse juno. Set the JBOSS WS run time location by following steps.
Window->Preferences->Web Services->JBossWS Preferences->Add. Then provide a name (eg. jboss-eap-5.1.0), Home Folder should be $JBOSS_HOME (which is the jboss-as folder). JBOSS server is EAP 5.1.0.
When I right click on existing wsdl to generate client code I get below exception.
Not sure why tools is not able to find JBOSSWS runtime location.
IWAB0014E Unexpected exception occurred.
java.lang.NullPointerException
at org.jboss.tools.ws.creation.core.utils.JBossWSCreationUtils.getJBossWSRuntimeLocation(JBossWSCreationUtils.java:296)
at org.jboss.tools.ws.creation.core.commands.InitialClientCommand.execute(InitialClientCommand.java:62)
at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359)
at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:254)
at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1028)
at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:264)
at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:91)
at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:154)
at org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136)
at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:908)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.wst.command.internal.env.ui.widgets.popup.DynamicPopupWizard.run(DynamicPopupWizard.java:130)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1053)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:942)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-14348) BrowserSim address string disappearing
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14348?page=com.atlassian.jira.plugi... ]
Yahor Radtsevich commented on JBIDE-14348:
------------------------------------------
In iOS Safari the address bar is connected to the top of the page and it appears/disappears slowly, part by part. We did not find an easy way to implement the same behavior in BrowserSim with SWT. This is the reason why the address bar disappears instantly.
The problem is that it the address bar begins to blink on some web sites if it is shown/hidden instantly.
> BrowserSim address string disappearing
> --------------------------------------
>
> Key: JBIDE-14348
> URL: https://issues.jboss.org/browse/JBIDE-14348
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.0.Alpha2
> Reporter: Daniel Azarov
> Assignee: Yahor Radtsevich
> Fix For: 4.1.0.Beta1
>
>
> Test case:
> EXECUTE:
> 1. Create project
> 2. Create html file:
> {code}
> <html>
> <head>
> </head>
> <body>
> <a id="page1">1 Jump to this place</a>
> <p>
> aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg
> </p>
> <a id="page2">2 Jump to this place</a>
> <p>
> aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg
> </p>
> <a id="page3">3 Jump to this place</a>
> <p>
> aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg
> </p>
> <a id="page4">4 Jump to this place</a>
> <p>
> aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg
> </p>
> <a id="page5">5 Jump to this place</a>
> <p>
> aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg
> </p>
> <a id="page6">6 Jump to this place</a>
> <p>
> aaaaaaaaa asdf ggggggggggg ggggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggggg ggggggggggggggggg gggggggggggggggg ggggggggggggggggggggg ggggggggggggggggggg ggggggggggggggggggggg
> </p>
> </body>
> </html>
> {code}
> 3. Open file with BrowserSim
> 4. Try to add #page3 to the address string
> FAIL:
> Address string disapeared
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months