-
Notifications
You must be signed in to change notification settings - Fork 756
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
Restore old functionaliy for some Quill toolbar classes #1633
Conversation
I restored only buttons which I used but there are other ones which are not fixed. So if button in web looks like before modifications it should looks like so after modifications but not like I tested example app so you may read #1628 (comment) for results. |
This issue can be solved without reverting, it's looks like the issue is caused by using the new Material 3 recommended widgets instead of the previous ones that work for Material 2 and 3, updating to 9.x.x require using Material 3 and the new widgets listed in Flutter 3.16 in additional to other changes. See the following for more details and suggestions: If you have any questions or suggestions, don't hesitate to create a new discussion or leave a comment here. |
Description
Today I have again spent time to make my project looks as it must. I do not do anything critical just restore the funcitonality of some toolbar classes as they were. You may consider this PR as a starting point for all other buttons which I didn't change. The only thing is required is change call of
QuillToolbarIconButton
inbuild
methods of embed buttons, search button and maybe others. You may see what I did. I also restored oldQuillToolbarSelectAlignmentButton
and save it asQuillToolbarSelectTextAlignmentButton
.I need this modifications to make my project compiled and continue working. You may merge this PR or use it for understanding how to make package backward compatible. It will take less effors.
Related Issues
Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?
!
in the title as explained in Conventional Commits).