[ 
https://issues.apache.org/jira/browse/OFBIZ-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875869#action_12875869
 ] 

Atul Vani commented on OFBIZ-3806:
----------------------------------

Hi Sascha, Jacques,

The code
this.target_element.up().style.height = e_height.toString() + "px";
was placed there believing that each input field will be contained inside of 
some other element,
and hence separated from other such elements,
like:
<some-elt>
  <input ... />
  <a href=""><img ... alt="cal-link" /></a>
  <div class="calendar">...</div>
</some-elt>
when we use form-widget, <td/> acts as <some-elt/>

the whole thing was done to limit the parent elements height, so that calendar 
don't shift things down.

one approach could be to fix the ftl forms. which might be a lengthy task.
another could be to find an alternate fix for 
https://issues.apache.org/jira/browse/OFBIZ-3667
which is more complicated then it looks, so what are your opinions.

Thanks & Regards
Atul Vani

> Calendar Layout in Product Feature Screen 
> ------------------------------------------
>
>                 Key: OFBIZ-3806
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-3806
>             Project: OFBiz
>          Issue Type: Bug
>          Components: product
>    Affects Versions: SVN trunk
>            Reporter: Sascha Rodekamp
>             Fix For: SVN trunk
>
>         Attachments: CalLayoutBug.jpg
>
>
> Hi,
> i found an issue in the calendar Layout (see Screenshot)
> [https://demo-trunk.ofbiz.apache.org/catalog/control/EditProductFeatures?productId=WG-9943]
> Maybe Someone have a quick fix.
> I located the issue in Calendar_date_select.js Line 134 but. I works to 
> commend the line out. But i don't know why this line was added.
> [code]
>     /* mod for OFBiz layered lookups*/
>     this.target_element.up().style.height = e_height.toString() + "px";
>     /* end mod*/
> [/code]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to