Timeline for On Chrome 49, component including link field cannot be saved
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 17, 2016 at 6:32 | comment | added | Rameshponna | Please refer below Answer tridion.stackexchange.com/questions/14200/… | |
| Mar 15, 2016 at 9:31 | comment | added | Raj Kumar | Hofixes available now | |
| Mar 9, 2016 at 20:39 | history | tweeted | twitter.com/StackTridion/status/707667159468675074 | ||
| Mar 8, 2016 at 13:38 | answer | added | Dominic Cronin | timeline score: 0 | |
| Mar 8, 2016 at 8:42 | comment | added | Nuno Linhares♦ | And to answer your 2nd question: if it works in every other browser, and in the previous versions of Chrome, it's probably not a Tridion defect. Chrome introduces breaking issues quite regularly, in Chrome 36 (or around that) they had a similar issue that got fixed a couple of versions later. | |
| Mar 8, 2016 at 8:35 | answer | added | Chris Morgan | timeline score: 1 | |
| Mar 8, 2016 at 8:21 | comment | added | Nuno Linhares♦ | We're looking at it. As soon as we understand what did Google break, we'll fix it. This also affects Web 8. | |
| Mar 8, 2016 at 6:41 | answer | added | Raj Kumar | timeline score: 5 | |
| Mar 8, 2016 at 5:15 | history | asked | Hirokazu Shikata | CC BY-SA 3.0 |