Alexandru Patrascu

This is the working example: https://stackoverflow.com/a/22271944/2068330

@bsweeney I replaced columns with tables. So now I have a table with a row and 3 columns. The problem is this: if the content of one column exceeds the...

@marrch-caat you can use display:inline-block instead of float, that will do. But the problem is if the content of the column in the left side goes on the next page,...

Did someone found a solution for this? I am searching for 3 hours and found nothing good related. I have the same problem with back button, js plugins like dropdowns...

It seems that the changes are already committed ([f233676](https://github.com/benwilkins/laravel-fcm-notification/commit/f2336762102173e50481c1b9a297fc9686cdd54f)) but not pushed on master. So to fix this you can simply get the dev-master: `composer require benwilkins/laravel-fcm-notification:dev-master`

If you store your key into services config, you can do this before creating the fcm instance (maybe in the notification constructor) `config(['services.fcm.key' => "NEW_KEY"]);`

Did you fixed this? I think is related to notifications that are sent into queues maybe?