mahara-contributors team mailing list archive

[Kristina Hoeppner <1973820@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Suggestion from Robert:

We have some very load intensive blocks that work with a lot of
JavaScript, e.g. the 'PDF' block and potentially also the 'External
media' block. Placing more than a few (less than 10) PDF blocks on a
page is fine, but more slows down pages a lot and is causing problems.

There are some options that we should investigate before making a final
decision:

1. Limit the number of load heavy blocks on a page.
2. We might need to get a load on scrolling type thing working, eg the block wrappers load on page load but the content loads via ajax only when the block becomes visible to the viewport - because we use gridstack now things should expand horizontally / float upwards as we want 
3. A combination of both.

With the progressive loading, we'd need to consider finding things in a
page and what the trade-off could be if someone uses Ctrl+F. It
shouldn't affect what is found via Elasticsearch.

** Affects: mahara
     Importance: Wishlist
         Status: Triaged

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: mahara-contributors
https://bugs.launchpad.net/bugs/1973820

Title:
  Limit the number of load-heavy blocks on a page or use progressive
  loading or both

Status in Mahara:
  Triaged

Bug description:
  Suggestion from Robert:

  We have some very load intensive blocks that work with a lot of
  JavaScript, e.g. the 'PDF' block and potentially also the 'External
  media' block. Placing more than a few (less than 10) PDF blocks on a
  page is fine, but more slows down pages a lot and is causing problems.

  There are some options that we should investigate before making a
  final decision:

  1. Limit the number of load heavy blocks on a page.
  2. We might need to get a load on scrolling type thing working, eg the block wrappers load on page load but the content loads via ajax only when the block becomes visible to the viewport - because we use gridstack now things should expand horizontally / float upwards as we want 
  3. A combination of both.

  With the progressive loading, we'd need to consider finding things in
  a page and what the trade-off could be if someone uses Ctrl+F. It
  shouldn't affect what is found via Elasticsearch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1973820/+subscriptions