Module talk:Adjacent stations/Amtrak

Atlantic City Express in Richmond

Please can a subject expert change the left terminus of "Atlantic City Express" to the code for the appropriate Richmond station? It currently makes links to the disambiguation page in articles such as Lindenwold station. (Show the former services at the bottom of the infobox to reveal the link.) Thanks, Certes (talk) 23:04, 11 February 2019 (UTC)[reply]

@Certes: Done. Mackensen (talk) 23:32, 11 February 2019 (UTC)[reply]

Thanks; that's sorted out all the dab's incoming links. Certes (talk) 09:50, 12 February 2019 (UTC)[reply]

Connecticut Valley Service

Lua throws an unknown line error when trying to use Amtrak as the system and Connecticut Valley Service as the line. Is this because it's just a redirect for the New Haven–Springfield Shuttle? –Daybeers (talk) 06:03, 23 April 2019 (UTC)[reply]

I'm not having any issue with North Haven station and Enfield station (Connecticut). (I'm not sure if other stations on the line should use it - it's basically the same service as the modern shuttle, just under a different name). Pi.1415926535 (talk) 07:02, 23 April 2019 (UTC)[reply]

Issue using aliases

I've had to change the line-based disambiguation for Albany and Centralia from "Amtrak Cascades" to "Cascades". For some reason, when aliases (like "Amtrak Cascades") are used as the disambiguator - even when they match here and when used in the template - the module just reverts to the default case. I assume that's an issue with Module:Adjacent stations? Pi.1415926535 (talk) 00:44, 24 June 2019 (UTC)[reply]

Yes, that would be an issue with core module. Interesting. I suppose it makes sense to not check aliases when using line names internally. Mackensen (talk) 01:08, 24 June 2019 (UTC)[reply]

Klamath Falls station

Something is up with the Adjacent stations in the navbox for Klamath Falls station. Note the links to the adjacent stations (Dunsmuir and Chemult) are not clickable. I've gone through the article to check syntax in the navbox parameters, and the lua code (though I only know enough to be dangerous) and can't find anything. Can someone more versed in finding syntax errors in code take a look? Dave (talk) 15:54, 12 March 2021 (UTC)[reply]

Moabdave, I'm not seeing the behavior you're describing. The links appear normal and work for me. Mackensen (talk) 18:32, 12 March 2021 (UTC)[reply]

Humm. OK, upon further investigation it appears to be browser specific. The page renders properly in Opera(mac), Chrome (PC),and even MSIE (PC), but not in Firefox(Mac) or Safari(Mac). When MSIE renders it properly but firefox doesn't Houston we have a problem. ;) Dave (talk) 00:35, 14 March 2021 (UTC)[reply]

I can't replicate the issue in Chrome or Firefox on Windows 10. Pi.1415926535 (talk) 00:47, 14 March 2021 (UTC)[reply]

I can't reproduce with those browsers on my Mac. Are you comfortable with the in-browser developer tools/Javascript console/things of that nature? This feels as though it's specific to your system, though I can't imagine how. Mackensen (talk) 01:35, 14 March 2021 (UTC)[reply]

@Mackensen: @Moabdave: Partially, it's not the browser. Whenever the stub template "train station-related article is a stub. You can help Wikipedia by expanding it." aligns horizontally with an adjacent stations link, the link is unclickable for me. Cards84664 07:48, 14 March 2021 (UTC)[reply]

Cards84664, right you are. Fascinating. The good news is this is already being discussed at Template talk:Asbox#Interaction between Asbox and Infobox. This may explain some weird behavior I was seeing at Lausanne–Bercher line earlier where the show/hide functionality didn't work at certain screen resolutions. Mackensen (talk) 13:11, 14 March 2021 (UTC)[reply]

And so it is, thank you, good detective work. Yes, I can confirm that by re-sizing the frames I can eventually get the links clickable in all browsers. So never mind, nothing to see here ;) Dave (talk) 17:47, 14 March 2021 (UTC)[reply]