As many of you know, the vehicle extension has moved out of tree and into the AMB source tree. Up until this point, the extensions could be both used since the vehicle namespace in upstream matched the W3C auto bg specification of navigator.vehicle as opposed to tizen.vehicle.
However, that assumption turned out to be not true. window.Zone entry point is provided by both and the extension server disables navigator.vehicle as a result. Here are my proposed solutions: 1 - Remove the tizen.vehicle extension 2 - Edit tizen-extensions-crosswalk.spec and make tizen.vehicle an optional subpackage Within tizen, all the apps that use tizen.vehicle have already been updated to use navigator.vehicle. This makes the impact of option #1 minimal. Suggestions welcome. -Kevron _______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
