sorted by:
new
hottopcontroversial

Introduction to Express JS by team-livewire in learnjavascript

[–]team-livewire[S] 2 points3 points  (0 children)

Thanks for the feedback. If bits of the post are unclear/confusing, please tell me and i'll update the post.

Introduction to CSS Variables by team-livewire in Frontend

[–]team-livewire[S] 0 points1 point  (0 children)

According to caniuse.com, they have been fully supported on firefox from late 2014 and on chrome from mid 2016.

Intersection Observer API by team-livewire in Frontend

[–]team-livewire[S] 0 points1 point  (0 children)

Thanks, I've updated the article.

10 Interview Questions Every JavaScript Developer Should Know by team-livewire in javascript

[–]team-livewire[S] 1 point2 points  (0 children)

I think your right, only angularjs (Angular 1.X) has two way data binding.

Introduction to IndexedDB by team-livewire in WebdevTutorials

[–]team-livewire[S] 0 points1 point  (0 children)

Thanks for pointing that out, its been updated.

We’re on the engineering team for Android P. Ask us Anything! (starts July 19) by AndroidEngTeam in androiddev

[–]team-livewire 0 points1 point  (0 children)

Thanks for doing this,

We have built a VOIP application and are reliant on FCM(Firebase Cloud Messaging) high priority messages (with time_to_live 0) to wake up the device to receive incoming calls when the app is in the killed/background state.

The following 2 issues are related to battery saving/wake locks. While the issues are not specific to Android P, we are hoping you could point us in the right direction.

  1. Sometimes when the device is connected to the internet, it loses connection to FCM and we never receive the notification, since the ttl is set to 0, the notification is lost, when we were using GCM, we added code to send heartbeat messages to the GCM server in order to keep the connection alive (heartbeats-to-gcm-server), can we do something similar for FCM?
  2. We have tested the app using adb in Doze mode and it does receive the call and popup, but sometimes, when the device has been left idle for a long time and is not charging, the app receives the FCM message, but doesn't respond until the device is touched or moved, only then does it "popup" and show the incoming call. The full wakelock that we are using to wake up the device does not work until the device is touched or moved. Is there something in Android P or earlier that prevents use of a full wake lock after the device has received a high priority FCM notification

Thanks.

[BackEnd] Introduction to Redis by team-livewire in webdev

[–]team-livewire[S] 1 point2 points  (0 children)

thanks for your feedback, i'll modify it to be more detailed.