Closed GoogleCodeExporter closed 8 years ago
It's all wrong. No need to highlight fields. Move the field box closer to the
highlighted shape so they don't need to scroll.
Original comment by zetapri...@gmail.com
on 6 Apr 2010 at 11:03
1. show the dotted lined for all fields when the mouse moves over the preview.
2. hide the dotted lines when the mouse moves out
3. when a field is highlighted and clicked on on the small preview show the
large
preview, keep the field highlighted and show the input straight away
4. add 3px white space around the current input and then a solid border of
sorts.
We'll come up with a better design in a few days. Can't see the input and can't
make
what they are when I see them. Same for image fields.
5. when a text input shows give it focus with a blinking cursor
6. There is no way to close an input. Some sort of a X will help.
7. Show the name of the field with the input.
Original comment by zetapri...@gmail.com
on 10 Apr 2010 at 10:19
Notice how the input area is shifted in relation to the highlighter.
Original comment by zetapri...@gmail.com
on 12 Apr 2010 at 4:04
Attachments:
Please, test it on magedev
Original comment by Anatoly....@gmail.com
on 13 Apr 2010 at 8:34
1. a bit more input field shift up and to the right to match the mockup
2. if a page is resized the input field moves somewhere
3. some input fields appear below the preview, outside the window and need to be
scrolled to
4. do not show field highlighters in small and large previews at the same time.
If a
large preview is in use then the small preview has no highlighters
5. when the large preview opens with an input field highlight the field
regardless of
the cursor position
6. once a field input is showing keep the highlighter and do not show the dotted
lines until the input is closed.
Original comment by zetapri...@gmail.com
on 13 Apr 2010 at 10:37
Original comment by agur...@gmail.com
on 13 Apr 2010 at 6:09
1. Try to show input field controls where the click was.
2. Try making the input field controls draggable.
Original comment by zetapri...@gmail.com
on 14 Apr 2010 at 8:52
1.Some of the floating text fields have an extra white border at the end of the
text
input field (floating_text_fields.png).
Depending on the weight of the field, sometimes it is more noticeable
(floating_text_fields2.png) and sometimes it is not there
(floating_text_fields3.png).
2. Highlight fields are not positioned correctly on multipage templates
(multipage1.png).
Try it here:
http://www.zetaprints.com/magedev/index.php/realestate-signs/fsbo-signs/multipag
e-testing-02.html
Go to the second page and hover above the preview image. Same thing happens to
all
pages except for the first one.
Original comment by agur...@gmail.com
on 15 Apr 2010 at 2:09
Attachments:
1. This is known problem with width of input fields. Same as on a product page,
2. Reason of the problem is wrong shape coordinates in the template details.
Original comment by Anatoly....@gmail.com
on 15 Apr 2010 at 3:28
== Image scroll doesn't work ==
http://www.zetaprints.com/magedev/index.php/email-signatures/email-signature-03-
detailed-300-x-100-px.html
Try to scroll. It all jitters and stays the same.
== Do not submit the form on ENTER in a pop-up field =
== Update the large preview if the small one got updated ==
Original comment by zetapri...@gmail.com
on 16 Apr 2010 at 8:41
Original comment by zetapri...@gmail.com
on 18 Apr 2010 at 8:47
Bugs are fixed in 1.8.1.0beta2. Test it on magedev.
Original comment by Anatoly....@gmail.com
on 22 Apr 2010 at 5:11
There is no fields highlighter on /magedev/
Original comment by agur...@gmail.com
on 25 Apr 2010 at 9:56
Original comment by Anatoly....@gmail.com
on 25 Apr 2010 at 10:20
Just the IE problem.
Original comment by agur...@gmail.com
on 25 Apr 2010 at 11:29
Original comment by Anatoly....@gmail.com
on 2 May 2010 at 4:28
Issue 2 in Comment #8. Since the err is in the shape coordinates in template
details,
the rest is OK.
Original comment by agur...@gmail.com
on 3 May 2010 at 3:44
Item 2 in comment 8 talks about known issues.
That's cool, but we need to log them and mark as ZP issues.
Original comment by zetapri...@gmail.com
on 4 May 2010 at 4:50
Original comment by zetapri...@gmail.com
on 4 May 2010 at 10:16
Item 2 in comment 8 is now in issue#203
Original comment by agur...@gmail.com
on 6 May 2010 at 8:42
Original comment by zetapri...@gmail.com
on 7 May 2010 at 12:18
Original issue reported on code.google.com by
zetapri...@gmail.com
on 6 Apr 2010 at 10:48