Dynamic Lighting problem with only one of my players

Hello. I've recently subscribed to supporter for dynamic lighting. And I am beginning to start a campaign, and have been doing some solo scenarios with each of my players to get them started. So far, two have been able to experience dynamic lighting in all it's glory, but when I brought in the third player he does not see anything. All black. I've made sure dynamic lighting is turned on, I've made sure fog of war is turned off, I've had the player reload, and restart. I've double, triple, and quadruple checked to make sure he has sight and light. When I highlight his token and press ctrl+L I see it properly but he does not. When I move him to a map without lighting and just fog of war, he sees everything fine. So we've narrowed it down to a dynamic lighting issue. He is using Firefox. Any help at all would be much appreciated!

Just to be sure, you've checked the "has sight" box on their token and made sure to assign that token to them to control?

Yep. I have two players in right now, one can see, the other cannot. Both have the same options checked.

Does this player have problems seeing when you have dynamic lighting enabled, but line of sight turned off? Also, another dumb question, does his token emit light or is it near enough to a light source that he should see it?

He had problems when dynamic lighting was turned on, regardless of line of sight being on or not. And I tried it with many different light sources around him and with him generating light. Now he has no problem seeing (He said after a minute of sitting there it just worked, but for a good hour yesterday and an hour today he couldn't), but I have another player with the same problem. In addition, when I switch maps now sometimes I see pure black until I reload my browser (Firefox), as a GM.

Is everyone using Firefox?

Not everyone. The one player who was able to see from the beginning was using Google Chrome

Paul , please send me a join link and I will take a look.

Thank you Gauss for the solution. Seems I overlooked giving the player permission to his own character. Always the simple things. The problem is now resolved.

Happy to help. :)