Comments (4)
@ewolf47 For standard fields we should go with the solution you suggested above:
In this case the hint would be visible as long as there is no content present in the form-field. Which means, if the user wants to see a hint he can always clear a field to make the hint visible again.
For the annotation and description field (see #3151) the hint must always be present.
from metadatamanagement.
Is this approach in your best interest?
As briefly discussed with @AndyDaniel1 in the webconf I commited this approach to the feature branch
from metadatamanagement.
@AndyDaniel1
a small note: for fields that display a red error message if the input is not valid (e.g. mandatory fields), I would still remove the hint text once the field has been interacted with (see "Titel (auf Englisch)") in the animation below). If the hint text would always be displayed, it looks kind of strange, because the info from the hint text is basically duplicated with the error message (see "Titel (auf Deutsch)" in the animation below).
Is this approach in your best interest?
from metadatamanagement.
✔️
from metadatamanagement.
Related Issues (20)
- Propagated DOI-Link seems to be incomplete HOT 2
- LaTex Template issue related to sponsor field HOT 2
- da|ra registration seems to be broken HOT 9
- Fix or remove websocket feature HOT 1
- Attribute source reference for questions
- Add Author & additional citation details for instrument attachment types questionnaire & variable questionnaire
- Add standard citation for questionaires HOT 7
- Generation of the data set report fails HOT 9
- Convert Components to new Angular Version
- Add filters for new attributes resulting from #2770 & #3257 HOT 2
- LaTex Report generation failed again HOT 2
- Error message "server is not available" when importing publications HOT 7
- Database: Permitted Use Cases for all data packages
- How to receive further information of publication ("journal" and "issue") HOT 1
- Display data as .json does not work anymore
- Landing page for hidden n/a data packages and elements nested withhin the data package
- Findability in OpenAlex.org HOT 1
- Model access conditions with DDI
- on test system accessways are not displayed anymore -> no ordering possible
- Metadata Export no longer works / Alternative implementation
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from metadatamanagement.