[Silk UI Mobile] SectionGroup only sticky 2 section title, the rest is not...

[Silk UI Mobile] SectionGroup only sticky 2 section title, the rest is not...

  
Forge Component
(17)
Published on 19 Oct by OutSystems R&D
17 votes
Published on 19 Oct by OutSystems R&D

Here's my SectionGroup:

Resulting screen:

Scroll a bit:


Scroll again to Gold Sponsor..


Then to Silver Sponsors:


Last 2 Section still have Platinum Sponsors as sticky.


Regards,

Harlin.

Hello Harlin!

I can't seem to replicate this behavior from my end. 

Can you send me an oml with the bug?

Hi, it was part of complex apps with dependencies to core entity module etc, so it's not simple for me to attach OML.

What I suspected is on my webblock there is an aggregate, which is run asynchronously.

I will try to fetch data in the parent screen, so webblock can rendered section content fast.

Hi Rita,

I have tried any static section group (including with images), but it won't replicate that behaviour.

So I create 2 OML:

1. TestSectionGroupEntry.oml (web) to bootstrap needed records, then upload each picture files.

2. TestSectionGroup.oml (mobile apps)

which show Section Group with ListItem and Section retrieved from database.

This is picture files attachment.


Steps to replicate:

1. Publish TestSectionGroupEntry.oml

2. Publish TestSectionGroup.oml

3. Run TestSectionGroupEntry, then click Bootstrap button

4. For each record, click to edit and upload appropriate picture file from attached zip file.

5. Run mobile app TestSectionGroup, tried to scroll down.


Note:

1. There is a JS error: Cannot read property 'children' of null

This error was not in my original app, only appeared in this sample app.

Maybe my original app have a logic to suppress this error somewhere, since many developers also worked on it.

2. Sometimes SectionGroup behaves right (about 10% of the time), but if you refresh the screen, it will misbehave again.


Thanks in advance.

Hello Harlin,

We've been able to replicate the behaviour, this happens because sticky headers are not native to androids/browsers for example and so we have a code that mimics its behaviour. We're going to review our code and hopefully release a fix soon.

Thanks and have a good afternoon :)