View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004541 | OXID eShop (all versions) | 3.2. HTML, CSS, JavaScript | public | 2012-09-21 10:51 | 2018-12-05 10:48 |
| Reporter | leofonic | Assigned To | |||
| Priority | normal | Severity | trivial | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 4.7.0_5.0.0_beta2 | ||||
| Summary | 0004541: Overview link is positioned absolute to page | ||||
| Description | "#overviewLink a" is positioned absolute to #page, so if #content or #details are moved by changing css, #overviewLink has to be repositioned. It would be better to declare #details position: relative, so #overviewLink would be absolute to #details. | ||||
| Steps To Reproduce | Change css height of #header. #overviewLink is misplaced. | ||||
| Tags | No tags attached. | ||||
| Theme | Not defined | ||||
| Browser | All | ||||
| PHP Version | Not defined | ||||
| Database Version | Not defined | ||||
|
|
Having absolutely or relatively positioned #ovierviewLink are both bad design decisions, it's palace is in the right corner of breadcrumb.tpl, even language constant name indicates it [{ oxmultilang ident="WIDGET_BREADCRUMB_OVERVIEW"}]. To solve this issue the right way we should add this link to smarty capture tag in details.tpl, and insert in in breadcrumb.tpl, on page construction, and adjust css to it. |
|
|
Why not just move the code to breadcrumb.tpl then? ...OK i see you would have to check for classname then. But maybe it would be clearer than a capture. |
|
|
Azure only. Not reproducible in Flow. -MK |
