Description:

• A-Frame Version: <script src="../../../dist/aframe-master.js"></script>
• Platform / Device: Windows, Google Chrome Version 81.0.4044.113
• Reproducible Code Snippet or URL:
  All of the text demos linked in components/text

Error message:

Uncaught TypeError: navigator.xr.requestDevice is not a funct

Priority

Low

Issue Description

In the screenshot below, LAST MODIFIED shows Sat, 26 Oct 1985 08:15:00 GMT,which is incorrect.

Expected Results

LAST MODIFIED shows correct timestamp, so that users know when this file is modified.

Screenshots/Related files

![image](https://user-images.githubusercontent.com/25629006/52917615-75906980-32a2-11e9-8825-10885a5955d2

Currently, the headless mode uses default parameters from PyChromeDevTools for connecting to a chrome headless instance.
https://github.com/maartenbreddels/ipyvolume/blob/e68b72852b61276f8e6793bc8811f5b2432a155f/ipyvolume/headless.py#L53
However, if you use a chrome headless running as docker instance and want to connect from another docker instance (e.g. when using docker-compose), the headl

In the Readme, there are confusing descriptions of the options.

One example:

sizeAttenuation - makes the line width constant regardless distance (1 unit is 1px on screen) (0 - attenuate, 1 - don't attenuate)`
lineWidth - float defining width (if sizeAttenuation is true, it's world units; else is screen pixels)

There's three things that are confusing here.

1. The name sizeAttenuation

Show camera navigation central point

Description

• Display central navigation point in the scene when using the orbit navigation mode.
• Should also apply to all derivated navigation methods.

Platform

• Web Version [X]
• Windows [X]
• Linux [X]

If I wanted to trigger the visibility of a nodes label/tooltip from an event that happened outside of the graph where should I start.

I can't see anything obvious in the node object to hook into to control the visibility of the label/tooltip.

Thanks!

Currently using the dots effect and wondering if there's any documentation for other options, or are the ones showcased on the website all that's available?

Currently docs are spread out and not interlinked. Make this coherent:

• pathfinding module
• controls docs
• misc/ folder
• navmesh blog post

^Maybe should just put all docs into README, moving forward?

Is your feature request related to a problem? Please describe.

I have project that use build systems other than webpack. It'd be great if Harp wasn't coupled to Webpack (or if the docs showed how to set up plain JS projects (with ES Module format is fine as most tools handle that part).

Describe the solution you'd like

Non-webpack users would want to follow a getting started guide

vue.runtime.esm.js?2b0e:4998 Uncaught TypeError: Cannot read property 'install' of undefined
    at Function.Vue.use (vue.runtime.esm.js?2b0e:4998)
    at createApp (app.js?1112:7)
    at eval (entry-client.js?a949:3)
    at Module../src/entry-client.js (main.js:2806)
    at __webpack_require__ (main.js:724)
    at fn (main.js:101)
    at Object.0 (main.js:2951)
    at __webpack_requi

Description

This link
http://jsfiddle.net/gh/get/library/pure/fnndsc/ami/tree/master/lessons/00#run
Is on the main page and ends up with a error 422?

Live Demo

Its in master above.

Steps to Reproduce

Follow the link

Expected Results

Loader example in jsfiddle as in the past.

Browsers Affected

• All
• Chrome
• Firefox
• Edge
• Sa

It is now mapped to the touchpad. After giving a lot of demos most people trigger the teleport by mistake and it's very confusing.

Is it known that the inspector is not longer opening using the keyboard shortcut on Windows machines? I'm running Firefox 71.0... I'm sure it's not just my computer as I had it checked by someone running the Udemy course I've been following.

Cheers.