Insi

I have multi-windowed webgl application which use the same texture atlases in each other. When 5-7 window opened I have a problem with performance and lack of video memory. Is it possible to economize video memory by sharing textures between windows? Or it happends by default? Or it's impossible in browser? - webgl inspector has no answers

Yeah, I've spent few days to do it without brim and have a failure - it don't want to work distinctly, sometimes it quit fullscreen after safari interface hidden and so on. Maybe something happends when viewport size in "viewport pixels" compared with window size in real pixels amount - like any problem with fractional size round. Don't know how brim do this so strict. May be it's some kind of magic Anyway in brim sources you could find a lot of things which I never want to do by myself, like hardcoded sizes of each ios device in both states (fullscreen and "window")

Does it suitable only for mouseover event? I have nothing similar with up/down/click events.

Also something works buggy in chrome since 4.4.1 (I don't check it on 4.5.x)

Oh, it works on desktop chrome, but doesn't work on mobile chrome Now trying to get it works. UPD: solved with timeout 150ms, but it doesn't looks reliably

Okay, I've found workaround on v.4.4.4. Just focus html input with timeout (could be zero timeout) setTimeout(_input.focus.bind(_input), 0); Cheers

4.4.4 - htmlinputs still not focusing by calling focus() from interaction with pixi sprites. Maybe any workarounds for 4.4.1+ ? Stuck on 4.3.4

In my app fullscreen will starts when user interacts whole screen (there is no "fullscreen button"). So I've solve the problem this way: 1. Put renderer to div: _fullscreenTarget = document.createElement('div'); document.body.appendChild(_fullscreenTarget); _fullscreenTarget.appendChild(_renderer.view); 2. Add event listener click/tap to div 3. Disable pixi's autoPreventDefault to catch events on div this._renderer.plugins.interaction.autoPreventDefault = false; 4. When eventListener called just run my old fullscreen mechanism document.documentElement.webkitRequestFullscreen(Element.ALLOW_KEYBOARD_INPUT); 5. Stupid browser thinks that it's legal unlike when canvas interacted

Unfortunately the same - mobile chrome doesn't show keyboard. Mobile safari still working ok )

Same problem on my own fullscreen mechanism, since chrome 56. Tested on a few Android 4-7 devices. Looks like Google thinks that we shouldn't use webgl elements to enter fullscreen

Is any news on it?

Pixi 4.4.2:http://analyst-carter-61864.bitballoon.com/ Pixi 4.3.4: http://estates-officer-polecat-75377.bitballoon.com/ Click on sprites calls focus() on HTMLInputElement to show native keyboard Mobile safari: both verison OK Mobile chrome: 4.3.4 OK, 4.4.2: keyboard never appear, but if you click a lot of times you could see flickering "keyboard icon" in system tray UPD: I've attach sources html5tests.zip

4.4.2 - problem still here

Same problem, chrome. I've create my own topic but then found this OK, I'll just paste my report here: I have pixijs webgl app with some inputs. I have an input which uses native html input which placed out of scene and dispatches some events to my input and so on (like old pixi.input project) Yesterday I've update pixijs from 4.3.5 to 4.4.1, and input has broken. When hidden input is focused and I've move mouse (like usual text selection) native unfocus event has been emmited on my hidden input without stack trace (by browser as I think). Keydown events also doesn't work on hidden input (maybe it previously unfocused by mouse up or mouseclick event after it has been focused). Pixi 4.4.1 Chrome - bug Mobile chrome - bug Mozilla - ok Desktop Chrome with mobile emulation - looks OK, but didn't test it enough Downgrade to Pixi 4.3.5 - all browsers works OK

I have pixijs webgl app with some inputs. I have an input which uses native html input which placed out of scene and dispatches some events to my input and so on (like old pixi.input project) Yesterday I've update pixijs from 4.3.5 to 4.4.1, and input has broken. When hidden input is focused and I've move mouse (like usual text selection) native unfocus event has been emmited on my hidden input without stack trace (by browser as I think). Keydown events also doesn't work on hidden input (maybe it previously unfocused by mouse up or mouseclick event after it has been focused). Pixi 4.4.1 Chrome - bug Mobile chrome - bug Mozilla - ok Desktop Chrome with mobile emulation - looks OK, but didn't test it enough Downgrade to Pixi 4.3.5 - all browsers works OK