Github user justin-mcdavid-ibm commented on the issue:
https://github.com/apache/couchdb-fauxton/pull/761
Hey Garren-- This is looking great.
Beyond the changes we talked about on video conference, here are some
things I've noticed while playing around. And I'm having problems getting
remote->remote replication to work (I'm getting permissions errors that I'm not
expecting), and local->remote are failing to complete. So I'm not able to test
some thing at this time.
# Activity Page
1. In-field text for "Filter replication" is 16px. Please reduce to 14px.
And let's get rid of the input box's padding; the box doesn't need to be so
visually dominant.
2. Remove the "Ok" button on error-message dialogue boxes
3. To slightly improve readability, can we strip the first set of curly
brackets off of displayed error messages?
4. The Edit Replication (wrench) functionality breaks if the replication
document ID starts with a forward slash.
5. Can we have the Activity page column-sort default to State Time,
descending from new-to-old?
6. When you add the refresh options to the header, could you make sure that
column-sort selection persists over refreshes or when the back-button is
clicked? When I refresh via the browser, it's resetting my sort selection.
# New Replication Page
1. The "Clear" replication-clear-link text is 16px. Please reduce to 14px.
Also increase the left-padding of replication-clear-link from 12px to something
like 12px 0 12px 24px (ow whatever will move it a similar distance to the
right).
2. On hover for truncated long values in dropdowns, can we have the full
value display?
3. Remover the API URL button from the header on this page, too.
4. Change the title of the Replication Error dialogue to "Fix Document
Conflict." Capitalize the first letter of the first paragraph in the message.
Add the eraser icon (http://fontawesome.io/3.2.1/icon/eraser/) to the
"Overwrite Existing Document" button.
5. Malformed remote source/target URLs prevent a replication from being
sent off when the Start Replication button is clicked, but there's no indicator
of why the job failed. Can we add highlighting to URL fields that are
malformed once the Start Replication button is clicked?
# Component issues?
1. Long db names in the local-db dropdown list are hidden behind the slider
(this is a component issue?). We should either give them some right-padding so
that the slider doesn't cover them, or allow horizontal scroll in the window.
2. The ellipses in truncated long values are running into the arrow on the
right side of dropdowns. Truncating a character or two earlier would likely fix
the issue.
3. In the fields of the form, font colors are not consistent between
selected text (#333) and entered text (#555). Let's make them a consistent
#333, to match the label color.
4. Related, the ellipses for truncated values should also be #333 (they're
currently picking up the color of in-field text).
5. The .Select-arrow-zone icons are not consistently colored, and don't
have consistent color states. They're #000 with no hover state before a value
is selected. After a value is selected, they change to #999, with a hover state
involving an odd border-top color-change. Hovers of #F3812D in Cloudant and
#E73D34 for CouchDB would be better for all dropown-select arrows, as well as
for the field-clearing Xs, as we have in the Replication document field.
# Odd Ways to Break Things.
1. If I create a job and specify a custom replication doc of /// the
Replication Activity section fails to to load. If I go into _replicator and
delete the doc, it comes back. A couple of hours later, I now can't reproduce
this, so it might have been a system hiccup. Or an odd bug that just happens on
first /// creation.
2. If I create a job and specify a custom replication doc of """ the
replication doc never updates, even though the replication job completed.
Thanks again for all the work on this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
