Skip to content
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

[META] CKEditor/Rich text editor followups #1087

Open
23 of 39 tasks
quicksketch opened this issue Aug 4, 2015 · 24 comments
Open
23 of 39 tasks

[META] CKEditor/Rich text editor followups #1087

quicksketch opened this issue Aug 4, 2015 · 24 comments

Comments

@quicksketch
Copy link
Member

quicksketch commented Aug 4, 2015

This issue summarizes follow-ups to the new WYSIWYG/rich text editor issue #101.

Todo:

Done:

@docwilmot
Copy link
Contributor

re #938 I feel if we get the "filter tips" in a modal as planned, the text format selection area will be completely acceptable without the collapsed fieldset, so is it worth the extra click then?

@klonos
Copy link
Member

klonos commented Nov 30, 2015

I've updated the list to add a couple of issues reported by @Graham-72, fixed a minor typo and removed a duplicate entry (issue 1125).

@Graham-72
Copy link

Please may I register a plea that these CKEditor issues now become high priority. You have done a brilliant job with release 1.3.0 for which I am very grateful, but CKEditor is a large part of the face of Backdrop to my end users, and if there are things it cannot do or gets wrong my end users are not impressed.

@ghost
Copy link

ghost commented Jan 17, 2016

👍 to @Graham-72 post : The missing Save button and plugin, the missing Autogrow plugin, are not understandable by my end users; they'd say it's not serious.
Ok, this is trivial to implement in a custom module, but not every one in small non-profit organisations have the option to write a single line of php (or the dozen of javascript lines to size the CKEditor area to the useable screen height)...

@quicksketch
Copy link
Member Author

Moving this to 1.5.0 for further work. We upgrading CKEditor in 1.4.0 to version 4.5.9. We still have several items needing addressing.

@quicksketch quicksketch modified the milestones: 1.5.0, 1.4.0 May 15, 2016
@docwilmot
Copy link
Contributor

Just a note, this is not the kind of thing I can handle, so I cant lend a hand here. But it would be great if this could be actually assigned to someone (or someones, since that's now possible), so that it doesnt just sit. I'm not sure (I hope I'm not being too presumptuous) how many of us are able to actually handle this. Would be great to see a show of hands here before we run out of time again.

@jenlampton
Copy link
Member

jenlampton commented Aug 11, 2016

I'm removing the bullet for "Add the ability to reuse an existing image on managed file elements" since I don't really understand what that means. Are we talking about building a new managed file form element that would allow the same toggle between autocomplete / file browser / view? Just like we already have in the CKEditor image dialog?

Would someone who understands that request create an issue with an explanation (and link it here) so we don't forget what it means all over again? :)

@Graham-72
Copy link

create an issue with an explanation

I now have tried to do this at issue #2056 'CKEditor - add the ability to reuse an existing image'.

@jenlampton
Copy link
Member

jenlampton commented Aug 12, 2016

We already have an issue for that in our list: #1307 Allow reusing images in the Editor dialog

@Graham-72
Copy link

👍

@quicksketch quicksketch added this to the 1.6.0 milestone Sep 15, 2016
@jenlampton jenlampton added this to the 1.7.0 milestone Dec 15, 2016
@olafgrabienski
Copy link

olafgrabienski commented Jan 17, 2017

I've added some CKeditor related issues in the checklist which were missing (1206, 1595, 1926, 2176, 2476).

@quicksketch
Copy link
Member Author

We will have knocked off #2630 and #1206 in 1.7.0.

I'm not sure if we should keep bumping this to the next minor release, but honestly I like having it accessible/findable there. Bumping to 1.8.0 for now.

@quicksketch quicksketch modified the milestones: 1.8.0, 1.7.0 May 2, 2017
@jenlampton
Copy link
Member

I'm going to bump the milestone for the meta to 1.9, I agree I like having it in focus for people looking for our priorities.

@jenlampton jenlampton modified the milestones: 1.9.0, 1.8.0 Aug 18, 2017
@jenlampton
Copy link
Member

bumping milestone.

@jenlampton jenlampton modified the milestones: 1.9.0, 1.10.0 Jan 15, 2018
@quicksketch
Copy link
Member Author

Knocked out #2072 in 1.10.

@jenlampton
Copy link
Member

bumping milestone.

@klonos
Copy link
Member

klonos commented Nov 1, 2018

@jenlampton this is a meta-issue. Should we just change the milestone to 1.x-future to avoid having to bump it every time?

@jenlampton
Copy link
Member

Sounds good!

@klonos klonos modified the milestones: 1.12.0, 1.x-future Nov 1, 2018
@klonos
Copy link
Member

klonos commented Nov 1, 2018

Done 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants