search

strictdoc-project / strictdoc

Software for technical documentation and requirements management.
https://strictdoc.readthedocs.io/en/stable/
Other
159 stars 26 forks source link

RapiDoc visual issues #1400

Open stanislaw opened 1 year ago

stanislaw commented 1 year ago

We have two issues with RapiDoc now. We assume that the developers of RapiDoc have added these CSS solutions to accommodate for their use cases. However, in our context their edge cases start to show up, and we don't seem to be doing anything special with our integration of RapiDoc.

We could introduce some hacks against these situations, but we believe that it is better to report them to the RapiDoc developers. To summarize: if the RapiDoc widgets are designed for integration into other systems, their CSS should be self-contained and not rely on a surrounding context.

1. Bottom margin, which should not be there:

telegram-cloud-photo-size-2-5330217387326298221-x

telegram-cloud-photo-size-2-5330217387326298225-x

2. Vertical height problem when a container runs out of vertical space at the bottom of a requirement.

The styles :host are added by RapiDoc's JS, note the height: 100%;.

telegram-cloud-photo-size-2-5330217387326298231-y

When we disable height: 100% manually, we start seeing the container to be displayed correctly.

telegram-cloud-photo-size-2-5330217387326298237-y

villanella commented 1 year ago

The corresponding RapiDoc issue - https://github.com/rapi-doc/RapiDoc/issues/976

stanislaw commented 11 months ago

@villanella just a small heads up: are you still interested in having this feature in StrictDoc?

When positive, consider reopening the RapiDoc issue https://github.com/rapi-doc/RapiDoc/issues/976 against the maintained fork repository as suggested in this comment: https://github.com/rapi-doc/RapiDoc/issues/968#issuecomment-1817164967. There is a chance that the fork developers could address it sooner.