Timeline for Software design for an Angular highlight&comment tool
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 14, 2021 at 18:28 | comment | added | Ben Cottrell | On further thought, since DOM editing is your functional requirement and the DOM being altered is your users' data rather than part of the app, then it doesn't doesn't really seem to matter whether you modify the DOM in-place. There are also a lot of Angular libraries out there for Angular WYSIWYG HTML editor components which you could refer to. Perhaps the more important issue is ensuring that whatever you're doing has sufficient automated tests around it. | |
| Nov 14, 2021 at 17:55 | comment | added | Ben Cottrell |
Angular itself is designed to avoid that kind of "traditional" DOM hacking. If your users' data is essentially raw HTML, then Angular supports dynamic components (ComponentFactory) which can be used to re-render a component every time its content or structure changes. The difficulty might be that removing a component from the display while the user has it focused then re-drawing could disrupt their UX, so make sure you consider things like element focus and cursor position otherwise your users will very likely notice and it could result in a lot of irritation for your users.
|
|
| Nov 14, 2021 at 16:25 | review | Close votes | |||
| Nov 29, 2021 at 3:03 | |||||
| S Nov 14, 2021 at 15:01 | review | First questions | |||
| Nov 14, 2021 at 15:50 | |||||
| S Nov 14, 2021 at 15:01 | history | asked | Bora | CC BY-SA 4.0 |