<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><br></div><div>please be reminded.</div><div>felix*</div><div><br></div><div><br></div><div>On 13.08.2010, at 19:22, Felix Kopp — PHORAX wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div>Hey Steffen & all the others,<div><br></div><div>alright I have now attached the discussed version (2).</div><div>Let me describe and summarize all included changes:</div><div><br></div><div>* The reset button (#treeFilterReset) in the page tree filter box is repositioned (little to the right, little to the bottom) to be centered</div><div>* The filtering JS is only included when the page browser hasFilterBox</div><div>* The tree filter input field (#treeFilter) is shortened by some pixels — there should be a some space between the reset button and long input (please see attached screenshots)</div><div><div>* The treeFilterReset does not require an additional fadeOut due to the fadeOut on parent div (#treeFilterBox)</div><div><br></div><div>* The filter input and filter is reset when the filter-icon is clicked</div></div><div><br></div><div>I guess this is the optimal behavior.</div><div><br></div><div><br></div><div>Tested on Safari 4, Firefox 3.6, Internet Explorer 7.</div><div><br></div><div><br></div><div>Looking forward to seeing this patch in the core soon :)</div><div><br></div><div>Warm regards from Hamburg,</div><div>Felix*</div><div><br></div><div><br></div><div></div></div><span><15294-v2.diff></span><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div></div><div><br></div><div><div style="color: rgb(60, 65, 77); font-family: Helvetica; font-size: 12px; "><b><font class="Apple-style-span" color="#36414D"><div style="color: rgb(60, 65, 77); font-weight: normal; "><span class="Apple-style-span" style="color: rgb(54, 65, 77); ">..............................</span></div></font></b></div><div style="color: rgb(60, 65, 77); font-family: Helvetica; font-size: 12px; "><font class="Apple-style-span" color="#36414D"><br></font></div><div style="color: rgb(60, 65, 77); font-family: Helvetica; font-size: 12px; "><font class="Apple-style-span" color="#36414D">TYPO3 aus Hamburg.</font></div><div style="color: rgb(60, 65, 77); font-family: Helvetica; font-size: 12px; "><font class="Apple-style-span" color="#36414D">Certified TYPO3 Integrator</font></div><div style="color: rgb(60, 65, 77); font-family: Helvetica; font-size: 12px; "><font class="Apple-style-span" color="#36414D"><br></font></div><div style="color: rgb(60, 65, 77); font-family: Helvetica; font-size: 12px; "><font class="Apple-style-span" color="#36414D">TYPO3 Association Supporting Member</font></div><div style="color: rgb(60, 65, 77); font-family: Helvetica; font-size: 12px; "><font class="Apple-style-span" color="#36414D"><br></font></div><div style="color: rgb(60, 65, 77); font-family: Helvetica; font-size: 12px; "><span class="Apple-style-span" style="font-family: Helvetica; "><div><font class="Apple-style-span" face="Arial" size="3"><span class="Apple-style-span" style="font-size: 12px; "><font class="Apple-style-span" color="#36414D">------------------------------<br></font></span></font></div><div><font class="Apple-style-span" face="Arial" size="3"><span class="Apple-style-span" style="font-size: 12px; "><font class="Apple-style-span" color="#36414D"><br></font></span></font></div></span></div></div><div><br></div><div><br><div><div>On 30.07.2010, at 16:46, Steffen Kamper wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hi Felix,<br><br>Felix Kopp — PHORAX schrieb:<br><blockquote type="cite">Hi Steffen-K,<br></blockquote><blockquote type="cite">actually I don't think so, otherwise all fly-out menus in the top bar had to act that same way.<br></blockquote><blockquote type="cite"><br></blockquote><br>i have a different opinion.<br><br><blockquote type="cite">Then on closing any fly-out the contained content should be reset.<br></blockquote><blockquote type="cite">(a) Open / Recent documents<br></blockquote><blockquote type="cite">(b) Shortcuts<br></blockquote><blockquote type="cite">(c) Search record<br></blockquote><br>no. The fly-out menus behave wrong - they are normal menus and shouldn't stay open when mose leaves. This will change when they are replaced by real menus.<br><br><blockquote type="cite">I personally think that the current behavior is good.<br></blockquote><blockquote type="cite">User's should be able to hide the filter-fly-out to minimize visual noise without quitting the function.<br></blockquote><blockquote type="cite"><br></blockquote><br>this behaviour would be ok if the display is inside the collapsing panel, but here you see the pagetree filtered. Collapse for having more space is no argument, space doesn't change, so why should you collapse?<br><br>So imho we have 2 possibilities:<br>1) reset the filter but leave the input filled, on next open you might use it again<br>2) reset the filter and reset the input<br><br>vg Steffen<br>_______________________________________________<br>Before posting to this list, please have a look to the posting rules<br>on the following websites:<br><br><a href="http://typo3.org/teams/core/core-mailinglist-rules/">http://typo3.org/teams/core/core-mailinglist-rules/</a><br><a href="http://typo3.org/development/bug-fixing/diff-and-patch/">http://typo3.org/development/bug-fixing/diff-and-patch/</a><br>_______________________________________________<br>TYPO3-team-core mailing list<br>TYPO3-team-core@lists.typo3.org<br>http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-core<br></div></blockquote></div><br></div></div>_______________________________________________<br>Before posting to this list, please have a look to the posting rules<br>on the following websites:<br><br><a href="http://typo3.org/teams/core/core-mailinglist-rules/">http://typo3.org/teams/core/core-mailinglist-rules/</a><br>http://typo3.org/development/bug-fixing/diff-and-patch/<br>_______________________________________________<br>TYPO3-team-core mailing list<br>TYPO3-team-core@lists.typo3.org<br>http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-core</blockquote></div><br></body></html>