2022-11-30 Paragon Meeting notes

5 minutes

Infinite loop in Truncate

@Adolfo Brandes

• Do we really need this component? Current browser support for line-clamp (let alone text-overflow) is pretty widespread. It would avoid all the weird edge cases any javascript implementation is bound to have to deal with (like the linked issue).

  • There may be a CSS-only solution for this.

  • Raccoon Gang is looking into this.

5 minutes

Weekly Meeting Reminder

@Ned Batchelder (Deactivated) (not attending)

There’s an automated Weekly Meeting Reminder in the old shared channel (#old-paragon-working-group in Open edX Slack; #openedx-paragon-working-group in 2U). Can it be stopped? If you still want the reminder, it should go in the new channel.

• Reminders for the PWG agenda/meeting are helpful, can be re-created in the connected channels.

• We’ll make sure the channel topic in the #paragon-working-group (2U Slack) points to new Open edX private connected channel.

•  

5 minutes

Floating form labels valid context evolution

@Jeff Witt (Deactivated)

5 minutes

Disabled control valid context evolution

@Jeff Witt (Deactivated)

Use tooltips?

5-10 minutes

Collapsible text box with TinyMCE

@Jon F

Is this a new component? Add-on to existing component?

Notes:

• TinyMCE is not currently implemented/supported in Paragon for technical reasons

  • https://github.com/openedx/paragon/pull/1131

    • Deferred because of these technical issues.

  • Paragon needs a reusable solution for a text editor that is better enabled to be supported in Paragon. issues with hosting files

    • Could we look into using Draft.js (or similar) to roll out own WYSIWYG type editor?

• There could be an opportunity to create a standalone component separate from Paragon for thic.

•  

@Ben Warzeski (Deactivated)

Is there a reusable way to track clicks on external links?

Should it live in Paragon? @edx/frontend-platform?

• Feels more like a @edx/frontend-platform thing.