Glad that you got it fixed. 95% of my bugs are simple and stupid stuff like that too. Yea, I always test my API fully on a browser before I ever go to C2.

https://drive.google.com/open?id=0B-xiq ... 0xDel9TRHM

Your PHP is probably fine. It is probably because of security measures that Construct takes seriously that most others don't.

You will want to add the " Access-Control-Allow-Origin: * " header to your server response in order for Construct to work nicely with the AJAX.

Make sure you remove that header again when you go live.

Do your clients need to push information back to your server? Because in most instances WebSockets is overkill. HTTP AJAX GET requests work excellent in 90% of places and they are a lot easier to get working.

You could try reporting the issue to the browser vendors, as described in the bug report guidelines.

Yea, I am doing that now.

right click on the add an choose Copy Link (or image) location? Or you can look into the HTML with a debugger.

gumshoe2029 I'm supporting it for the time being as far as bug fixes go, but as far as adding new feature I'm less inclined to do it to avoid increasing the bug fix support load (don't have that much time) and also, since it's already not that user friendly, I prefer keeping it simple.

if you have any issue, report it on github, it's easier for me to keep track of it over there.

Oh I hear you there. I keep singing my 99 bugs on the wall song.

Sad days.

Apparently, Whatsapp does not have an application program interface, but you can use the Yowsup library for Java/Python to push messages to WhatsApp.

So you would have to do AJAX or WebSockets back to a Java/Python server and let the server push the messages to WhatsApp.

Someone's summoning bloody fingertips right there xD

Lol, it was a suggestion. They never gave me any indication whether they actually took it or not.

Hmm... where did I heard that before...

(lol sorry, couldn't stop myself. Just joking around )

Lol, well played.

I think you may be being trivial calling it a re-skin. From what we know it's being rewritten to work on multiple os and with new features.

Who are you to say that it should take x amount of time and no more?

I didn't call it that. Ashley did.

The full screen stuff is because all browsers require input (like mouse click or screen touch) to activate full screen mode, but you're right, that doesn't explain the black screen.

Now I can't replicate it, lol. I was juggling a lot of instance variables too though, so I suspect I had some crossover causing confusion.