t3olayout issueshttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues2022-04-04T14:44:42Zhttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/612Use FF70+ on Mac (or also windows?) conflicts with placeholder texts2022-04-04T14:44:42ZStefan BusemannUse FF70+ on Mac (or also windows?) conflicts with placeholder texts### Summary
If you se FF70+ on Mac (or also windows?) conflicts with placeholder texts, when the username / password is stored in FF.
### Steps to reproduce
1. Use Firefox 70+
1. Login into typo3.org or my.typo3.org
1. store the pa...### Summary
If you se FF70+ on Mac (or also windows?) conflicts with placeholder texts, when the username / password is stored in FF.
### Steps to reproduce
1. Use Firefox 70+
1. Login into typo3.org or my.typo3.org
1. store the password
1. Log Out
1. open the login dialog
### Example URL
https://my.typo3.org
### What is the current *bug* behavior?
Placeholder Text is overlaying stored Username / password values
### What is the expected *correct* behavior?
only the placeholder or stored username / password
**Acceptence Criterias**
* [ ] Placeholdertext are not visible, if value of username or password is available
### Relevant logs and/or screenshots
![image001](/uploads/401d961520b83ff46fdc9522d78bf060/image001.png)Backloghttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/621Processed/compressed image resource are not used on client device2022-04-04T14:46:50ZOliver HaderProcessed/compressed image resource are not used on client devicee.g. https://typo3.org/article/recap-of-the-combined-sprint-of-typo3org-and-server-team/
Independent of which screen resolution or device simulation is used, the full fallback image is downloaded (Google Chrome Version 76.0.3809.100 on ...e.g. https://typo3.org/article/recap-of-the-combined-sprint-of-typo3org-and-server-team/
Independent of which screen resolution or device simulation is used, the full fallback image is downloaded (Google Chrome Version 76.0.3809.100 on macOS). I'm experienced the same on a native iOS device (iPhone & iPad) connected with 3G.
By looking at the responsive images part, it becomes obvious that no image processing is happening. All source-sets deliver the same original image.
> I guess image processing is not configured properly on typo3.org, most probably the settings for a development container are different to the production website which is not reflected in `.env` or `AdditionalConfiguration.php`
```
<picture>
<source srcset="/fileadmin/t3o_common_storage/news/2019/05/2019-05-22-Combined-Sprint-Stuttgart-Team.jpg" media="(min-width: 1200px)">
<source srcset="/fileadmin/t3o_common_storage/news/2019/05/2019-05-22-Combined-Sprint-Stuttgart-Team.jpg" media="(min-width: 992px)">
<source srcset="/fileadmin/t3o_common_storage/news/2019/05/2019-05-22-Combined-Sprint-Stuttgart-Team.jpg" media="(min-width: 768px)">
<source srcset="/fileadmin/t3o_common_storage/news/2019/05/2019-05-22-Combined-Sprint-Stuttgart-Team.jpg" media="(max-width: 767px)">
<!---Fallback--->
<img class="img-fluid" title="TYPO3.org- and Server-Team" src="/fileadmin/t3o_common_storage/news/2019/05/2019-05-22-Combined-Sprint-Stuttgart-Team.jpg" width="3095" height="2060" alt="" />
</picture>
```
![Screenshot_2019-08-15_at_17.39.34](/uploads/f34ccc5374f58332866548e61d65f4e8/Screenshot_2019-08-15_at_17.39.34.png)Backlog