-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Option to disable the anchor field #82
Comments
You are very welcome @arnaudjuracek! Glad you find my plugin useful 🙏🏻 I like your idea and I'm going to implement this not only for the anchor, but also for every other field. It's a bit more challenging to keep the layout consistent. Not every field takes the full width, but I'm confident to find a proper solution :) |
@arnaudjuracek Before I'm going to start to work on this issue I need to clarify what do you mean by |
IMHO the UX is better for the user when the field is completely hidden, but you may have other scenarios in mind where disabling the field makes more sense ? Thanks for your time. |
Okay, let's do both ^^ The user can decide whether he wants to |
You can now control whether the anchor or target field should be disabled or hidden, allowing for a cleaner and less obtrusive link dialog. Closes #82
You can now control whether the anchor or target field should be disabled or hidden, allowing for a cleaner and less obtrusive link dialog. Closes #82
You can now control whether the anchor or target field should be disabled or hidden, allowing for a cleaner and less obtrusive link dialog. Closes #82
# [3.2.0](v3.1.3...v3.2.0) (2023-04-16) ### Features * add options to control anchor and target field visibility ([051855d](051855d)), closes [#82](#82)
🎉 This issue has been resolved in version 3.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
@arnaudjuracek Let me know if this feature works for you :) |
First of all, thank you for your plugin. It is so simple that I may use it by default on all my new Kirby projects, until it ends up being eventually integrated to the Kirby core.
It would be really nice to have a config option to disable the anchor field, to allow building simpler websites for unskilled clients who do not need to know what an anchor is.
The text was updated successfully, but these errors were encountered: