Who am I?
My name is Maya and I am from the Portal support group.
The main task of our group is to solve bugs in the product – so we’re only supposed to receive messages about actual bugs.
This is not always what happens in reality. Many of the cases that initially seem to be bugs end up being an issue with configuration or incorrect usage.
One of the important activities that we have in our group is to reduce these kinds of messages and save time both for you – the customers – and for us (fewer messages = less work J).
So the purpose of this blog is
- Share these issues with you – interesting cases that I encounter in the course of my support work that can be solved either by using a workaround or with correct configuration as well
- New bugs which either I or my team colleagues fix.
And how can you help me with this?
- By distributing this blog to other portal customers.
- By suggesting cases that you think could be interesting for everyone – either cases that you solved on your own or issues that were solved through messages – you can add your suggestions in the comments section of this blog.
The first case that I want to share with you is an issue with portal support for Chrome.
So let’s begin…
It’s been a long time since my last post – but I think it was worth waiting!
I made a thought research on the standard/quirks issues of the Portal since IE started supporting standard mode, and summarized it in the following blog:
Hello to my followers,
I just published a new blog about an interesting case I’ve investigated.
It’s about how you should perform navigation in the Portal.
here’s the link:
I published a new blog which is related the Portal and IE rendering issues.
It’s about rendering issues when running an iView in standalone mode.