WEBURL button rendering issue on Chrome

[Martin Smith]

Hi,

On Chrome (I'm using v87) the button for a weburl seems to be shown under the field instead of to the right of it. I think it's a browser issue as it looks correct in IE.

Can anyone suggest a workaround that's compatible across browsers?

EDIT: sorry forgot to mention I'm using OX 6.4.1.

Thanks,

Martin

[Javier Paniza]

Hi Martin:

I tried with Chrome v86 an it works well, as attached.

I tried to upgrade Chrome to v87 but it says that it is already up-to-date, seems that my chrome thinks that v86 is the latest one.

When was Chrome v87 released?
Did you try with Firefox or Edge? Does it work with them?

---

Help others in this forum as I help you.

[Martin Smith]

Hi,

Thanks for replying. Chrome v87 is the upcoming dev branch I think. I'm seeing the same issue on Firefox (72.0.1) and Edge.

Martin

[Javier Paniza]

Hi Martin:

I don't achieve to reproduce it.
Could put here your @View declaration indicatin what is the WEBURL property?
Are you using flowLayout=true in xava.properties?

---

Help others in this forum as I help you.

[Martin Smith]

Hi,

I do have flowLayout=true. Turning that off seems to fix the problem.

The view definition is below, the WEBURL is named sourceUrl.

Thanks,

Martin

  @View(members= "general [#" +
      " name;" +
      " type;" +
      " thumbnail;" +
      " size;" +
      " rating;" +
      "];" +
      "purchase [#" +
      " supplier;" +
      " cost;" +
      " productCode;" +
      " sourceUrl;" +
      " available;" +
      "];" +
      "dates [" +
      " dateAdded;" +
      "];" +
      "notes [" +
      " description;" +
      " notes;" +
      " reviews;" +
      "]")

....

  @Stereotype("WEBURL")
  @Column(length=8192)
  private String sourceUrl;

[Javier Paniza]

Hi Martin:

I do have flowLayout=true.

So we have found a bug. Please ad it with a link to this thread and we'll fix it for future releases.

---

Help others in this forum as I help you.

[Martin Smith]

OK, thanks. I created a bug.

Martin

[Javier Paniza]

Hi Martin:

This bug is already closed and its fix will be in v6.4.2. Coming soon.

[Martin Smith]

OK, thanks for letting me know.

Martin