Github user justin-mcdavid-ibm commented on the issue:
https://github.com/apache/couchdb-fauxton/pull/864
Hey Garren,
Lookin' good! That section is rather slick. I see a few lingering issues,
and a handful of things to polish, and then I think we're good.
Something has changed broken alignment of the values in the replication
form:
And the width for the dropdown values is still not matching the width of
the dropdown field (for both source and target local dbs):
The doc-conflict buttons could still use some extra space (20px) between
them:
I noticed that the job-deleted banner message (and message in the
notification center) is picking up more than just the replication number:
The length is such that I noticed a lack-of-wrapping bug in the
notification center, which is something I'll open up a bug on.
Can we strip off the non-job-id information in that job name, and add a
period to the end of the statement?
**Some polish and tweaks:**
With only one Action icon on the _replicate Activity table, I think it
would be better to align it under the column header:
I realize that "everybody" permissions terminology is going to be confusing
for those who've set permissions using the CL, where the user is "nobody." For
the last paragraph in this hoverhelp, I'd like to change the statement to "If
the remote database granted permissions to unauthenticated connections, you do
not need to enter a username or password."
Let's align the (now shorter) caveats with the text in the first content
column (Source) in the tables. I think that would be 80px from the left.
It would be nice to swap out the white-check icon for the previously used
replication icon:
And swap the white-check icon on the verify-deletion buttons for trashcan
icons:
Thanks for your 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 [email protected] or file a JIRA ticket
with INFRA.
---
