As identified in #550428: Tags like " " or "<p> </p>" or "<br />" added to empty textareas., we should create a list of known issues somewhere.
The question is:
1) Where?
2) In which format?
3) How to structure it?
4) Who should be able to change/update/extend it?
5) What to cover (and what not)?
--
Some environmental data upfront:
- Known issues for Wysiwyg module should be mostly the same for D5/D6/D7, since also the code is almost identical.
- Some existing known issues likely get solved with every new release (e.g., 2.2).
- New issues may arise with new features (e.g., in 2.3).
- Most known issues are relevant for one or more particular editor libraries only.
- The existing FAQ might already contain entries that may rather be known issues. (not verified)
Comments
Comment #1
R2-D8 CreditAttribution: R2-D8 commentedjust brainstorming...
1)
a) Basic and classic: attached files in an issue called "List of known issues". Maybe managed via svn.
b) Outsourced: On a new wiki-like Drupal-Installation out in the web.
c) Drupal.org-Implemented: 8) (Where do I have to communicate such issues best?)
a) could be started now; b) within hours; c) ??
2)
a) input: not clear yet - but if inbound into systems maybe .csv or .xml
b) output: Multiple formats - rss if possible.
4)
If = 1a): Only the project maintainers
If >= 1b): Sounds like a wiki;
3 and 5 are very unclear now - but these points are fixed with each other and can grow.
So what can be done now:
More clearance about the, as you said, environmental data upfront.
I think a simple data structure like the following demo-entry would be fine:
Comment #2
TwoDTo keep things simple for now, I've added a "Known Issues" section to the FAQ that currently lists regressions in the latest release.
Comment #3
steinmb CreditAttribution: steinmb as a volunteer commentedIs this something worth spending time on keeping up2date? Not changed since 2017 - https://www.drupal.org/node/417166/revisions