Premium support for our pure JavaScript UI components


Post by gaurav.tyagi »

Hello,

I am trying to use the requestFullScreen method to show the scheduler in the full screen mode, but the event edit pop-up does not appear in the front of screen in full screen.
Please find the attached project for the reference.

Thank you.

Attachments
custom-event-editor.zip
(149.32 KiB) Downloaded 39 times

Post by mats »

Please share your JS code so we can review it.


Post by gaurav.tyagi »

Hello Mats,

I have not made any custom JS updates, I have simply added a button called requestFullScreen() function on click of it.
I could reproduce the issue with that change only.


Post by mats »

Can you please submit your button code?


Post by gaurav.tyagi »

Hello Mats,

Please find the attached example.
Button is in app.component.html file.

Thank you.

Attachments
custom-event-editor.zip
(398.34 KiB) Downloaded 66 times

Post by alex.l »

Reproduced, thank you for clarifications. Here is a ticket to track the status: https://github.com/bryntum/support/issues/4622

All the best,
Alex


Post by saki »

You can change the approach that's used by our demos. I've tested it and it works:

import { Scheduler, Fullscreen } from '@bryntum/scheduler/scheduler.lite.umd.js';

// ...

    changeToFullscreen(){
        Fullscreen.request(document.documentElement);
    }

Post by gaurav.tyagi »

Hello Saki,

I found the requestFullscreen function here :
https://bryntum.com/docs/gantt/#Core/widget/Widget#function-requestFullscreen

I will try to change the approach and let you know the result.

Thank you.


Post by gaurav.tyagi »

Hello Saki,

I tried the approach suggested by you.
It works fine if I pass the document.documentElement as parameter in the request function, but if I pass some other htmlElement as parameter then it also have the same issue (tooltip and editor pop-up does not work).

I have attached the sample project for reference.

Thank you.

Attachments
custom-event-editor.zip
(404.92 KiB) Downloaded 38 times

Post by mats »

@gaurav Please try adding your custom event editor element to our float root (an element with CSS class '.b-float-root') - this should fix the issue.


Post Reply