V7 Portlet does not render when setHeight("100%") is used #3698

Closed
vaadin-bot opened this Issue Mar 21, 2013 · 5 comments

Projects

None yet

1 participant

@vaadin-bot
Collaborator

Originally by dnebing


Attaching Liferay project and portlet war file for your review...

com.vaadin.bugs.BugTest1UI creates a VerticalLayout, adds some labels, then sets the VL as the content for the ui. This will render fine in the portal.

com.vaadin.bugs.BugTest2UI does the same thing, but it sets the height for the VL to 100%. This portlet will not render in the portal.

Checking the rendered contents, the div for the "v-app liferay" (the main app div) has a height of only 1 pixel. Since it is only 1 pixel, the outer div for the portlet-body is also 1 pixel.

If I manually change the height if the "v-app" div to a fixed value (say 200px), the content renders. If I set the height of "v-app" to 100%, it will not render (parent elements are still only 1 pixel).


Imported from https://dev.vaadin.com/ issue #11394

@vaadin-bot
Collaborator

Originally by dnebing


Attachment added: v7-test-portlet.zip (34.5 KiB)
Source project for the submission.

@vaadin-bot
Collaborator

Originally by dnebing


Attachment added: v7-test-portlet-6.1.1.1.war (31.0 KiB)
War file for Liferay 6.1.1 CE GA2 (the lcepatchers.org edition).

@vaadin-bot
Collaborator

Originally by dnebing


BTW, I'm using Liferay 6.1.1 CE GA2 (the version from lcepatchers.org which has a number of Liferay patches applied). Widgetset is defined in portal-ext.properties to use com.vaadin.DefaultWidgetSet. Version 7.0.3 is installed in the portal per instructions on the website, and widgetset has been compiled. Clearing the cache has no impact.

@vaadin-bot
Collaborator

Originally by dnebing


Setting a breakpoint on com.vaadin.server.WebBrowser.updateRequestDetails(), I can see that it does get invoked w/ appropriate dimension information, so the server side does have the dimensional details necessary to render sizing info...

@vaadin-bot
Collaborator

Originally by @Artur-


A lot of tickets have been left hanging in the issue tracker through the years. Some of them are still relevant, some of them have been fixed a long time ago and some are no longer valid. To get a better look on what is important and still relevant, we are closing old tickets which have not been touched in a long time.

No further work will be done on this ticket unless someone indicates that it's still relevant.

If this ticket is still relevant to you, please reopen it.

@vaadin-bot vaadin-bot closed this Dec 17, 2014
@vaadin-bot vaadin-bot added the bug label Dec 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment