#28271 closed defect (bug) (fixed)
wpviews: TinyMCE buttons that aren't relevant should be disabled
| Reported by: | iseulde | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | TinyMCE | Version: | 3.9 |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
You can't align it, make it bold, quote it etc. Might be best to disable everything and enable buttons that still are relevant (redo/undo, help...).
Change History (6)
#1
@
12 years ago
- Summary wpviews: TinyMCE buttons that aren't relevant to should be disabled → wpviews: TinyMCE buttons that aren't relevant should be disabled
#4
@
10 years ago
- Keywords close removed
- Milestone Awaiting Review → Future Release
I think this is something TinyMCE should handle
Since wpviews are very custom, I tend to disagree. Plus, we'd need a tracking ticket anyway.
Expecting this to be handled internally when TinyMCE implements the "widgets" feature.
IIRC this happened in the meantime, no?
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Makes sense especially for buttons that can be "disabled" in other cases. Expecting this to be handled internally when TinyMCE implements the "widgets" feature. In the meantime we can probably try to make a quick patch :)