Metadata
- Source
- FLUID-1201
- Type
- Bug
- Priority
- Major
- Status
- Open
- Resolution
- N/A
- Assignee
- Colin Clark
- Reporter
- Jacob Farber
- Created
2008-08-19T12:51:35.000-0400 - Updated
2017-01-16T09:40:50.857-0500 - Versions
-
- 0.5beta1
- 0.5
- 0.6beta1
- 0.6
- 0.7
- 0.8
- 0.8.1
- 1.0
- 1.1
- 1.1.1
- 1.1.2
- 1.1.3
- 1.2beta1
- 1.2
- 1.2.1
- 1.3
- 1.4
- 1.5
- 2.0
- Fixed Versions
- N/A
- Component
-
- Reorderer
Description
When using relative measurements in a reorderable situation (i.e. width : 50%), the avatar will likely look off due to those relative measurements being out of context flow.
A possible solution to this would be to use a snapshot of the node's computed style.
Comments
-
Antranig Basman commented
2008-09-10T22:45:50.000-0400 (pasted from fluid-work email)
After a bit of tinkering, I think I must unfortunately conclude that the
"avatar shrinkage" issues cannot be a matter for the Reorderer but can
only be dealt with in user CSS. Basically the user has so much control
over the avatar markup that really only they can know and apply a
correct strategy for setting its size. I tried to forcibly stick CSS
width properties onto the avatar as it is created, but really it doesn't
listen (in the portal sample) - the div and CSS structure of the portal
element is just too complex for the information to trickle down correctly.Perhaps Jacob can correct me on this, but right now my feeling is that
we will have to close FLUID-1201 as unworkable... we can certainly
extract the relevant height and width of the "old portlet" but I can't
see at the moment how we could ensure the avatar will listen, or create
a strategy so it will. -
Jacob Farber commented
2009-06-05T09:32:10.000-0400 I could be wrong, but if you assign the style attribute of the avatar container to be the width and height of the "old portlet" as mentioned, it should probably adhere to those dimensions regardless of what anyone else has in their CSS (at least, css specificity rules would suggest so)