Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.9K Databases
- 221.6K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.9K SQL & PL/SQL
- 21.3K SQL Developer
- 295.4K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.1K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 397 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 230 Portuguese
Text in fields disappeared/became invisible when page item in focus/clicked on.

APEX vesion 20.2
Chrome version 94.0.4606.81
Using Universal Theme - 42
This issue only happened a week or so ago and only on Modal windows. Upon clicking on a field (e.g. text field or select list), the text becomes invisible. For text fields, you cannot see what you are typing but upon losing focus of the field, the text becomes visible.
This is not happened in Normal Windows, only Modal.
This seems to happen after upgrading to Chrome v94 but cannot be sure if that is the cause.
It is also not happening on all machines with the same version of Chrome. Also, it does not happen on Firefox and IE/MS Edge.
Have anyone encountered this?
Best Answer
-
Thanks for setting the record straight. While trying to fix this issue, I was actually trying to do a little bit more - when I click on the a field, I wanted an oragne border around the field. Somehow, if I set the border for the non-focused classes to 1px, the solution didn't work.
This is my full CSS:
.apex-item-select, .apex-item-text, .apex-item-textarea {
-webkit-transition: all 0.2s ease;
-moz-transition: all 0.2s ease;
-ms-transition: all 0.2s ease;
-o-transition: all 0.2s ease;
border: 1.1px solid #dfdfdf;
}
.apex-item-select:focus, .apex-item-text:focus, .apex-item-textarea:focus {
border: 1px solid #f7921e;
outline: #f7921e solid 1px !important;
}
Anyway, I tried it with only the "focus" CSS and it will work with just 1px border e.g.
.apex-item-select:focus, .apex-item-text:focus, .apex-item-textarea:focus {
border: 1px solid #dfdfdf;
}
Answers
-
Hi, I'm facing the same strange issue.
I also use Chrome version 94.0.4606.81 and it happens on one machine while not on another with the same chrome version. I also tried MS Edge, which is not affected by this behaviour.
The modal pages become practically unusable over night.
Does anyone have an idea?
Thanks!
-
Apex versions 20.2 and 21.1
Chrome version 94.0.4606.81
We are also experiencing exactly this issue - Chrome v94, with both Apex v20.2 and v21.1, on both Mac and Windows. However only some users are encountering it, not all of us are able to reproduce it, despite being on the same version of Chrome. Firefox and Edge are fine.
-
I managed to work around this issue by applying custom CSS. Still none the wiser as to the cuase.
I applied the following custom CSS to the theme roller and the problem went away. Not the most elegant of solution but I needed to fix it fast.
.apex-item-select, .apex-item-text, .apex-item-textarea {
border: 1.1px solid #dfdfdf;
}
If the border is 1px, the disappearing act happens so I set it to 1.1px and it stop disappearing.
-
The inline CSS didn't work for me. The border gets set but that doesn't change the behaviour on click.
-
If you try adding ":focus" onto the end of each item in the list - it should take effect when the item receives the focus
.apex-item-select:focus, .apex-item-text:focus, .apex-item-textarea:focus {
border: 1.1px solid #dfdfdf;
}
-
Perfect, that solution worked. Thank you very much!
-
Thanks for setting the record straight. While trying to fix this issue, I was actually trying to do a little bit more - when I click on the a field, I wanted an oragne border around the field. Somehow, if I set the border for the non-focused classes to 1px, the solution didn't work.
This is my full CSS:
.apex-item-select, .apex-item-text, .apex-item-textarea {
-webkit-transition: all 0.2s ease;
-moz-transition: all 0.2s ease;
-ms-transition: all 0.2s ease;
-o-transition: all 0.2s ease;
border: 1.1px solid #dfdfdf;
}
.apex-item-select:focus, .apex-item-text:focus, .apex-item-textarea:focus {
border: 1px solid #f7921e;
outline: #f7921e solid 1px !important;
}
Anyway, I tried it with only the "focus" CSS and it will work with just 1px border e.g.
.apex-item-select:focus, .apex-item-text:focus, .apex-item-textarea:focus {
border: 1px solid #dfdfdf;
}
-
Hello everyone I have the exact same problem. Is there any more in-depth solution ???
-
This version of the CSS fix helped us. Thanks Creg and Bigal!
.apex-item-select:focus, .apex-item-text:focus, .apex-item-textarea:focus { border: 1.1px solid #dfdfdf; }
The "orange" version that Bigal suggested only worked for us on some page fields, but not all. Also, we had to put the 1.1px on the border because with the 1px it didn't work on any of the affected fields.
We can't pinpoint the cause. We are all on the latest Chrome build and some of us have the problem, some don't. Also, our Windows builds are all over the place so that doesn't help us either; on my PC, Version 10.0.18363 Build 18363, it works, on an older Build 15-something and a never Build 19-something it doesn't .
-
This is an interesting bug, I am curious for those running into this issue. What is your browser zoom level? Is this happening at 100% zoom level? If so... what is your operating system resolution/dpi set at?