mozillareality / firefoxreality Goto Github PK

FxR has a new back handler API for widgets. It's currently implemented for focus and full screen modes.

We should implement that too for settings and permission prompt dialogs

Browser window: ease the colors in and out to make it look a bit smoother than just abrupt color change

This check got commented while adding Tray support as it wasn't always returning. Probably related as how the collider normal is calculated. Research, fix and uncomment.

We need to improve the widgets API to create all the windows, widgets and placements from Java:

• Create & place all widgets from Java
• Generate ids from java in order to avoid having to wait the callback with the C++ handler
• Remove the widget creation enumerations
• Consider moving visibility to WidgetPlacement class
• Adapt all widget children to the new API

CXB-22 Currently you need to add the protocol to detect a URL, and it does a google search if you don't add it.

Check what other browsers do in order to detect when to automatically load a URL instead of a search.

• Improve the keyboard placement.
• Use the latest GV api for a better keyboard visibility detection

First click selects the whole text as we want but the next click doesn't set the cursor position and keeps selecting the whole text again

If FxR is started (via debugger or adb command line) on the Oculus Go while the display is off, it will fail to render when the display gets activate by the proximity sensor when donning the headset.

Is anyone testing against the Mirage Solo?

It's readily available and has 6dof head movement at least.

• Implement full-screen mode
• Enabled from chrome UI or from a JavaScript call
• Exit from full-screen mode

Enable immersive mode by supporting gfxVRExternal API.

Depends on https://bugzilla.mozilla.org/show_bug.cgi?id=1465816

I want to install the build on HTC Focus but I meet some errors when I built irt with Android Studio.
First the function onCrash() must be override in three classes in the project but it was easy to fix.
My main problem was with an error relative to the compilator I think. The error file is joined here.
I was really enthusiastic to use this app and I'm a beginner in android development so I hope it's an obvious beginner error.
ErrorBuildAndroidFocus.txt

Some letters in the keyboard aren't correctly aligned (e.g. the 'g' key). Center the letters on the x_height.

BrowserWorld is getting too big. Moving the controller management code to its own class would help make the class a little more manageable.

I just installed the new build on my Go and it crashed as soon as I clicked on one of the starting links. I realized I didn't have wifi on. Instead it should tell me that I need to connect to the internet.

I followed the instructions and built the project successfully, but when tried to run on my pixel 2, got the error: Device supports, but APK only supports armeavi-v7a

Some people tried the browser in the off-site and one of the comments about the keyboard was that the backspace position was confusing. People are used to have it above the enter key.

After leaving the app, in case you do not "continue" or "quit" and just do something else, the sessions (opened private sessions) are not correctly restored when app is reopened.

GeckView alpha cannot be changed so we'd need this to make the fade in/out effect in private mode for GeckoView.

Buttons can be left in hover state if the button is pressed and then released off of the button.

Set the correct text for the keyboard enter button based on the IME type of the textbox (done, go, search, etc.)

e.g: Enabling WebVR preference and loading the WebVR sample gets the "page says WebVR found but no displays available." on the first launch.
On next launches it runs ok.

The controller gets switched off and then never switched back on in BrowserWorld.

From: https://twitter.com/moocow1452/status/985525427555962888
Suggestion: I'm trying to get Prime Video on my Daydream using Firefox Reality, but it will only stream in Desktop mode. Could requesting a desktop version be an option in the final version?

It happens when launching from the icon or Android Studio.

Launching from head set works ok.

Set the right hover styles and text selection colors for the URL bar

Need to make sure and catch when gecko view is in fullscreen mode so that clicking the back button on the controller takes gecko view out of fullscreen mode instead of actually going back in history.

The remote controller pointer is very big when the widgets are close to the user. Currently we are hiding the pointer for the keyboard because of that.

Ideally we can adjust the scale to make the pointer the same size on any widget. We also can check for alternative designs (sphere?)

STR:

1. Go into private browsing mode (fade effect enabled)
2. Go into focus mode (fade effect enabled again [note there is a flash, probably shouldn't happen])
3. Go out of private browsing mode

Expect result: Fade effect remains.
Actual result: Fade effect is turned off.

Preferences/settings UI for telemetry, crash reporting, privacy policy

VRB now support asynchronous loading of models and textures. Add support to FxR.

The URL of the home page is a long URL (resource://......). It's not pretty for a product. Keep the URL bar empty or find a better text

The same for error pages.

Currently Telemetry is initialized every time the activity is created. It should only be initialized when the application is created. Please review Sebastian's PR and fix accordingly.

I feel stupid asking this, but after installing the released .apk on my Daydream compatible device I can use FirefoxReality fine as a mobile browser, but there seems to be no way to actually switch into VR mode?

Does it only work with the Daydream headset NFC tag? I am using a third party headset that doesn't come with this NFC tag, but all other Daydream apps can be switched to VR manually.

a shift key on the right enables me to type my passwords more quickly!

Please provide build/target for Windows Mixed Reality platform.

https://github.com/mozilla-mobile/android-components

As far as I understand, Android Component abstract Gecko/GeckoBeta/Webkit under a common interface. I was wondering if we could use that instead of the GeckoView directly?

Asking because we also want a Servo backend for Crow. And adding Servo along Gecko and Webkit in AndroidComponent feels like the natural thing to do.

/cc @MortimerGoro @jdm

STR:

1. Go fullscreen or focus mode

Expect results: tray is hidden
Actual results: tray is still visible

Research how to show android permission prompts on each device

On the old UI links with "target=_blank" opened a new tab. On the new UI, until the carrousel is ready, we need to stack the new link in the current session instead of setting a different session

STR:

1. Go into focus mode
2. Set window size to 3x
3. Leave exit focus mode
4. Go back into focus mode

Expected result: Screen should still be 3x
Actual result: screen is default size.

STR:

1. Go into focus mode.
2. Make scree 3x
3. Leave focus mode

Expected results: Close button updates position to be above browser window.
Actual results: Close button retains position from large focus mode window.

Start the new UI integration:

• Better window & widget sizes, placements, etc
• Single-window UI design (without carousel)
• New URL bar design
• Organize all the placement sizes & dimensions in a Android Resource file to make it easy to change

We need to create a popup to be able to type some keybord characters that aren't in the default querty layout

e.g. Possible flow to write á' would be to:

• Press and hold the normal a key
• After some threshold the keyboard shows a popup on top of the letter with all the possible variations for the selected letter (e.g. áăäâ)
• Selected the variation or close the pop up