Thinking more about it, we need to decide what we want:
* Keep using an anchor favor offering the better view for the content of the tab but
moving the page
* or not moving the page (not sure how to do it but I’m sure it’s possible) and letting
the user move down if he wants to see more
TBH I don’t know what I’d prefer, but you could be right that not moving the page would be
a better option.
Let’s see what others think.
Thanks
-Vincent
On 27 Aug 2016, at 12:21, Vincent Massol
<vincent(a)massol.net> wrote:
On 27 Aug 2016, at 12:17, Vincent Massol
<vincent(a)massol.net> wrote:
Hi Mars,
Thanks for sending those 2 images but could you explain in words what the problem is,
because I fail to understand it and we need to be able to reproduce if we want to fix
something.
I’ve tried to reproduce on XWiki 8.3 SNAPSHOT and indeed when a tab is clicked (comment,
attachment, history, etc) the page is moved.
This is because it’s implemented as an anchor
(
http://localhost:8080/xwiki/bin/view/Main/#Attachments) so the browser moves the page as
high as possible so that what’s after the anchor is visible to the maximum extent.
That seems a good thing to me. For example imagine you have 15 attachments. For example
try going to
http://platform.xwiki.org/xwiki/bin/view/Features/DocumentLifecycle#Attachm… and you’ll
see the page is moved up the max so that the max number of attachments is visible.
Not sure what you’d expect differently.
Thanks
-Vincent
Thanks!
-Vincent
On 27 Aug 2016, at 08:20, 既然 M.A.R.S
<464503882(a)qq.com> wrote:
<359033DD@32B5916E.4031C157.jpg><282EFA5D@32B5916E.4031C157.jpg>_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs