RE: 7.2 RC3 - Alloy Editor Source Mode Buttons Lack Background / Behind Tex

Lee Jordan, modified 6 Years ago. Expert Posts: 449 Join Date: 5/26/15 Recent Posts
This is depressing ... flick to code view in Alloy Editor. Buttons lack background color until hover. In 7.2 RC3 the buttons are positioned over the text. Sure moving the buttons above the content field works, but yet there's still no background color and they are lower in contrast to 7.0 / 7.1.
Also appearing behind text
thumbnail
Jamie Sammons, modified 6 Years ago. Expert Posts: 367 Join Date: 9/5/14 Recent Posts
Hi Lee,

It looks like this maybe a known issue: https://issues.liferay.com/browse/LPS-95880
Lee Jordan, modified 6 Years ago. Expert Posts: 449 Join Date: 5/26/15 Recent Posts
Is there any possible way that the product can ship without Alloy Editor until resources are given to test it inside DXP? It's very fine to test it on its own, but what is occurring that is allowing this software to behave the way it is inside DXP?
Even now just typing this I typed a line break and within a few seconds the line break was removed. Also the cursor shot to the start of the line?
thumbnail
Jorge Ferrer, modified 6 Years ago. Liferay Legend Posts: 2871 Join Date: 8/31/06 Recent Posts
Hey Lee,As I have mentioned in the past we value your feedback and passion about Liferay very much. In this case and related posts from yesterday you are crossing the line of respect. Saying things such as "Depressing", "until resources are given to test", ...  are just judgements and exaggerations that I believe are unfair to the people working on this.I'll be happy to continue interacting with you whenever the feedback follows reasonable manners.
Lee Jordan, modified 6 Years ago. Expert Posts: 449 Join Date: 5/26/15 Recent Posts
Yes very sorry for that conversational tone. Alloy is very important to the user experience it hurts to see the regressions so close to release.
thumbnail
Jorge Ferrer, modified 6 Years ago. Liferay Legend Posts: 2871 Join Date: 8/31/06 Recent Posts
Thanks for your response. Apologies accepted.I agree that AlloyEditor is very important. Let's work together to solve any issues. I think it would be best if you could create JIRA tickets for the issues with detailed reproduction steps and environment information (browser, etc). 
Lee Jordan, modified 6 Years ago. Expert Posts: 449 Join Date: 5/26/15 Recent Posts
Respectfully I think JIRA or at least isolated bug reports is part of the problem. The same or very similar issues keep regressing with Alloy and I'm honestly not sure if it's a separate project and it's tested and works outside of Liferay and then comes in and issues are seen. 
It feels like the latest release is pulled into Liferay DXP both 1.x for 7.0 and 2.x for 7.1/2.

Would a "stable", "unstable", "development" label to each version of Alloy help maintain stability within DXP? It feels like DXP is always getting the in progress version of Alloy. If say the editor isn't expected to achieve stability until 2.21 then keep the current version in DXP where it is until all the tests within liferay are done and the tests are passing before the version is incremented in Liferay.

Again I apologize for the use of language, it's pretty disheartening to have spent a year trying to communicate the issues with the editor and to see the same things and even new things keep coming back.
thumbnail
Jorge Ferrer, modified 6 Years ago. Liferay Legend Posts: 2871 Join Date: 8/31/06 Recent Posts
I understand how you might feel if you are finding a lot of bugs. Still, we have an efficient process to solve them if they are reported with enough details in JIRA. In addition to that, feel free to create forum threads linking the JIRA ticket if you want to have a wider conversation encompassing several of them and I'll ask developers working on it to participate. That way we get the best of both worlds.