Re: [Roundup-users] Problem with long pulldown (Link) menu on Firefox and Chrome not fully populating

[John P. R. <ro...@cs...>]

Hi David:

In message
<SA1P110MB19304D4AA4304EC9CE3BEDA2CCF8A@SA1P110MB1930.NAMP110.PROD.OUTLOOK.COM>,
"Hancock, David US Professional Services, Inc. \(USP\) via
Roundup-users" writes:
>First, I apologize for asking about such an ancient version of the
>software. This is Roundup 1.5.0 with classic templates. It’s not my
>choice, though.

Understood, I have helped somebody off list with a 1.4.x release so...

Can you verify that html_version in your tracker's config.ini is set
to html4. This is the default and I do not expect it would have been
changed.

>I’ve encountered a situation where Mac Safari displays a pulldown
>menu correctly, but Chrome and Firefox (also on Mac) do not. Chrome
>and Edge on Windows work correctly.

Ok, that's very wierd. Roundup doesn't customize its output based on
the client. The HTML for the menu should be the same for all browsers.

>I’ve got a DB class called fbcustcomp in schema.py as a Link type,
>which is populated with slightly more than 100 company names. The
>.item.html file for this issue type has a table row:
>
><tr>
><th class="required" nowrap>Company</th>
><td tal:content="structure context/fbcustcomp/menu">fbcustcomp</td>
></tr>
>
>In Mac Safari and Windows Chrome or Edge, the full list can be pulled
>down.

That TAL looks fine and since it works with the Safari and Chrome
engines, I am going to say it's valid. Does Firefox on Windows work ok
too?

Can you pull up the developer tools or view the source for the page on
one of these.

>In Mac Chrome or Firefox, the list is empty (“not selected”) on
>a new issue, and if an issue has been edited, there are exactly two
>items in the pulldown (“not selected” and whatever was saved in a
>browser where the pulldown works).

Please compare the dev tools/source on these failing browsers to what
is shown above.

This may give us an idea as to what's happening.

IIUC on a Mac, all browsers (chrome and firefox) use the same safari
engine. So I am surprised at this problem.

>Most of the users are on Windows and Mac Safari works right, so this
>is not even close to an emergency. But if anyone has any thoughts
>about this issue, I’m all ears.

Check to see if any errors are reported in the dev tools
console. There should not be any javascript involved in that select
box, but somebody may have modified it from the default
template. Again, since it works in safari, I expect it to work in
other Mac browsers.

Note, if you have sensitive data in the page this may not be an
option. You can try is to copy the page source and paste it into the
w3 html validator: https://validator.w3.org/. If it returns
errors/warnings, we may have another thing to look at.

>I’m also open to hearing “we haven’t got time to support a
>15-year-old Roundup—get yourself current!” I’ve got it coming.

A quick search for differences between 1.5.0 and the current head does
show a change in how some data is escaped. I'm not sure why this
change is present. So it could be a red herring. But nothing in the
diff leaps out to me as an attempt to change the generated menu HTML.

In any case, you should look into getting Roundup upgraded. OS support
for Python 2 may be a problem and 1.5.0 won't run under Python 3.

Hopefully this gives you some ideas for exploration.

Have a great day.
--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.