Jump to content


  • Content Count

  • Joined

  • Last visited

About ArtsyCraftsy

  • Rank
    Cool Cruiser

About Me

  • Location
    Bellingham, WA
  • Interests
    lace crochet, paper crafts, music composition, PEO, cooking, collecting cookbooks (~ 3800 so far)
  • Favorite Cruise Line(s)
    Regent Seven Seas, Holland America (so far)
  • Favorite Cruise Destination Or Port of Call
    Everywhere 😊

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. ArtsyCraftsy

    First World Cruise booked ...

    So glad I found this board! I'm a solo traveler, which can both complicate and simplify cruise travel sometimes. I'm also a "newbie" when it comes to cruise travel -- I've done only three cruises so far, two on Holland America: 14-days to Alaska, just to see if I would actually like cruise travel, 38-days to test my coping capabilities with a "longer" cruise; and one on Regent Seven Seas: a 28-day cruising combining Alaska with the Panama Canal to try a different cruise line. On the basis of that third cruise and while onboard (around day 11), I booked the Regent Seven Seas 2020 "Navigate the World" cruise: 131 days, starting and ending in San Francisco. The world cruise is on the same ship (the Mariner) and I was able to book the same cabin I was occupying at the time -- it was perfect for me: perfect size, perfect location, and great amenities I love the itinerary, and surprisingly, the basic RSSC fare is 20% less than the HAL 2020 128-day WC for a comparable cabin in terms of amenities despite RSSC's "all-inclusive" pricing. There's a difference in the itineraries: HAL's route goes around the coast of Africa; RSSC's goes through the Middle East and the Mediterranean, but I'm not sure that's enough to justify the cost difference. Add in the cost on HAL of drinks, excursions, gratuities, etc., and the difference is even greater. The primary factor in the price difference is the single supplement: RSSC's was about 45%; HAL's was 100%. By the time the World Cruise arrives in January 2020, I will have done three more cruises in 2019 (another HAL 28-day - Hawaii/Tahiti/Marquesas, an Oceania 7-day - Alaska, and a HAL 35-day - Incan Empires), and with each cruise, I learn more about packing, organizing, scheduling, etc. I read several of the boards here on CC daily and I'm always learning something. I've read through several of the threads so far and have started making a "to do" list -- many of the entries I had thought about (but had no idea what to do about them -- now I have some ideas!), and some I hadn't even considered. I have some health challenges and had a chat with one of my docs just this past week about reasonable preparations. Coincidentally, he and his wife cruise at least once a year, and he's totally on board (no pun intended) with my future cruise plans given my situation. We have over a year to prepare for this. I'm likely to have a LOT of questions over the next year, and I'm grateful to those "regulars" here who generously share their experiences. Thanks ... Lana in Bellingham, WA
  2. ArtsyCraftsy

    Beef Wellington?

    It showed up on the Compass Rose menu at least one night during my last cruise (28 days) -- it may have been on one of the "formal optional" nights, but honestly, I can't remember. They also had salmon Wellington one night, too. And yes, as Travelcat2 said, you can pre-order it (and almost anything else if you give them enough advance notice and they have the ingredients onboard).
  3. ArtsyCraftsy

    Google Chrome vs Safari

    Looking at the other messages in this thread, I don't think it's just me who is having the issue. I'm running a straightforward MacBook Air -- up-to-date OS, basic apps (Pages, Numbers, Google, Safari, etc.), no "developer"-type apps, etc. So I'm not convinced that "my" installation is that unique. It's likely the same as thousands of other MacBook Air Chrome installations. You're saying, I think, that no other website I visit "utilizes code that Chrome cannot accept in (my) configuration" -- in other words, out of hundreds of other websites I visit, it's just this one that utilizes the suspect code. That would imply that there's something unique about this particular application that is triggering ... something ... in Chrome that isn't present in hundreds of other applications that currently play nicely with Chrome. If that's the case, it would probably be a good idea to warn Chrome users that there just might be a compatibility issue. I've tried to provide as much info as I can for the folks who might find it useful (CC IT staff): OS version, Chrome version, etc., to help narrow down the specific issue. Without access to the code itself, I can't assume anything else. Saying it's the way I've installed Chrome on my specific machine doesn't really help me to solve it on my end, and doesn't provide anything useful to others who are experiencing the same issue. I've run the uninstall/install process provided by Apple and Google -- there's not much more I can do at this point. As I said, there's a workaround -- Safari -- that I can use until/unless this is resolved.
  4. ArtsyCraftsy

    Google Chrome vs Safari

    OK -- I've done all three of the suggested fixes (clear cache/cookies; reset to original; uninstall/reinstall). Chrome is stripped down to its original configuration (no extensions, no "themes," etc.). Still getting the error. It's puzzling that not all Chrome users are experiencing the problem. If it were purely a function of Chrome's misconfiguration, I would think all versions of it would be affected. My hunch is on some combination of operating system + Chrome. As I said, I've experienced no issues on any other website -- just this one. At least there's a workaround -- I can use Safari for just this website and use Chrome for everything else.
  5. ArtsyCraftsy

    Google Chrome vs Safari

    Interesting that Chrome, misconfigured and non-compliant as it is, has been working just fine under the old Boards software and the issue appeared only when the new software was installed. (It also works fine on every other site I visit, so ... ). Will try the "restore to original defaults" approach ...
  6. ArtsyCraftsy

    Google Chrome vs Safari

    I just tried using Chrome again and am still getting this error (started yesterday). I'm on a MacBook Air, running High Sierra version 10.13.6 (17G65) Google Chrome Version 70.0.3538.67 (Official Build) (64-bit) (Official Build) (64-bit) Here's the error I'm getting: Bad Request Your browser sent a request that this server could not understand. Size of a request header field exceeds server limit. Works fine on Safari; doesn't work on Chrome. Lana in Bellingham, WA